BobStore/F-Droid/lint.xml

<?xml version="1.0" encoding="UTF-8"?>
<lint>
    <!-- Remove severity="ignore" to see the missing translations -->
    <issue id="MissingTranslation" severity="ignore" />
    <issue id="TrulyRandom" severity="ignore" />
    <issue id="UnusedResources" severity="ignore">
        <ignore path="res/values/default_repo.xml" />
    </issue>
</lint>
Add lint.xml with ignores for MissingTranslation 2014-01-08 13:04:00 +01:00			`<?xml version="1.0" encoding="UTF-8"?>`
			`<lint>`
			`<!-- Remove severity="ignore" to see the missing translations -->`
use official Android methods to mark strings as "do not translate" Android's lint will give warnings for all strings that are not translatable or translated. Some strings like repo name/description and language codes should never be translated. Here's how to officially mark as "do not translate": * for individual strings, include: translatable="false" * for the entire file, name it: donottranslate.xml http://tools.android.com/recent/non-translatablestrings https://code.google.com/p/android/issues/detail?id=75163 2015-04-14 16:31:12 -04:00			`<issue id="MissingTranslation" severity="ignore" />`
ignore TrulyRandom lint warnings, fdroid already includes the fix PRNGFixes.apply() is run in FDroidApp.onCreate(). This is enough, according to Google, and their instructions say to disable this lint warning once the workaround is included since lint cannot detech whether the workaround is applied. This the code format was also automatically corrected by the Eclipse plugin 2014-08-01 23:13:39 -04:00			`<issue id="TrulyRandom" severity="ignore" />`
			`<issue id="UnusedResources" severity="ignore">`
Ignore UnusedResources on default_repo.xml We iterate over them programmatically, so lint thinks we don't use them 2014-03-17 09:39:52 +01:00			`<ignore path="res/values/default_repo.xml" />`
			`</issue>`
ignore TrulyRandom lint warnings, fdroid already includes the fix PRNGFixes.apply() is run in FDroidApp.onCreate(). This is enough, according to Google, and their instructions say to disable this lint warning once the workaround is included since lint cannot detech whether the workaround is applied. This the code format was also automatically corrected by the Eclipse plugin 2014-08-01 23:13:39 -04:00			`</lint>`