Lint (21 rc10) missing translation errors for English regions

103 views
Skip to first unread message

Alec Plumb

unread,
Oct 26, 2012, 6:22:05 PM10/26/12
to adt...@googlegroups.com
I have an app where the default language us US english. I also have translations for several other languages, and for these the "is not translated" lint error is invaluable. However, I also have a very few strings that I need to change for en-rAU and en-rGB, but lint complains "x" is not translated in en-rAU, en-rGB 200 times. Is there any way to tell lint that the default language is "en", so that it doesn't complain about missing translations for other english regions?

According to the Localization API Guide I am organizing my resources correctly, so it would be nice if lint didn't mark these as errors.

Xavier Ducrohet

unread,
Nov 8, 2012, 8:11:27 PM11/8/12
to adt...@googlegroups.com
We don't really have support to declare what the default language is at the moment. We should add this somewhere. I'll talk to Tor about it.


On Fri, Oct 26, 2012 at 3:22 PM, Alec Plumb <abp...@gmail.com> wrote:
I have an app where the default language us US english. I also have translations for several other languages, and for these the "is not translated" lint error is invaluable. However, I also have a very few strings that I need to change for en-rAU and en-rGB, but lint complains "x" is not translated in en-rAU, en-rGB 200 times. Is there any way to tell lint that the default language is "en", so that it doesn't complain about missing translations for other english regions?

According to the Localization API Guide I am organizing my resources correctly, so it would be nice if lint didn't mark these as errors.



--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com

Please do not send me questions directly. Thanks!

Tor Norbye

unread,
Nov 26, 2012, 3:20:46 PM11/26/12
to adt...@googlegroups.com
FYI, this will be addressed by https://android-review.googlesource.com/#/c/46834/ . In short, add tools:locale="en" to your <resources> element (but of course this will only be considered by the tools when you use the first Tools 22 Preview).

-- Tor
Reply all
Reply to author
Forward
0 new messages