forked from amazingfate/loongoffice
These should be managed automatically via weblate, s. [1],
so there shouldn't be any need to manually remove stale
strings for all translations.
There are 2 lint checks for these, `ExtraTranslations`
and `UnusedResources`.
Disable `ExtraTranslations` altogether.
The `UnusedResources` check seems useful in general,
so only disable that for the translations by adding
a lint config file `lint.xml` (s.a. [2]) using a
wildcard for the path that matches the translation's
string.xml files.
This is in preparation for
Change-Id: Icab66a1768f5c6250598fcf788377575d3f6f611
Author: Michael Weghorn <m.weghorn@posteo.de>
Date: Fri Dec 15 10:28:21 2023 +0100
android lint: Drop unused string resources
This also avoids that these will show up in Weblate,
causing unnecessary work for translators since they're
unused anyway.
IIUC, dropping the strings in already existing translations
should be handled automatically by Weblate.
(Leave them there to see whether this actually works as
expected.)
[1] https://gerrit.libreoffice.org/c/impress_remote/+/155966/comments/769f76c5_c3c499ec
[2] https://developer.android.com/studio/write/lint
Change-Id: Ic7c7a1c4c5583bf1a42004480435aac70a88dee0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160822
Tested-by: Jenkins
Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
10 lines
263 B
XML
10 lines
263 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<lint>
|
|
<!-- Disable check for extra resources in translations, Weblate takes care of
|
|
removing these. -->
|
|
<issue id="UnusedResources">
|
|
<ignore path="res/values-*/strings.xml" />
|
|
</issue>
|
|
</lint>
|
|
|