On Tue, Aug 13, 2013 at 11:45 PM, Kostya Vasilyev wrote:
> So you have an HTC... I've got two on my desk, and the language / locale
> list on both of them is region-specific:
>
> Russian (Russia, Ukraine, Georgia, other former Soviet republics)
> English (same list of countries)
>
> Other deivices
Apologies for replying to myself, just wanted add to my previous message
that I checked with my Optimus One. On that device, the L&I menu seems to
match getLocales() output (some filtering similar to what LocalePicker does
notwithstanding), however as it turns out, when I switched our app to "zh"
So you have an HTC... I've got two on my desk, and the language / locale
list on both of them is region-specific:
Russian (Russia, Ukraine, Georgia, other former Soviet republics)
English (same list of countries)
Other deivices I have (a couple of Samsungs purchased in Russia, another
Samsung fro
Admittedly it took a bit ;-) but I finally got around to taking a closer
look.
My HTC Desire show the following languages in its Languages&Input menu:
English (United Kingdom)
English (Ireland)
French
Italian
Spanish
Not a lot. However, when I call
Resources.getSystem().getAssets().getLocales(
latimerius wrote:
> True, if you are able/willing to supply a text renderer with your app
> surely there's nothing in devices that would prevent it from rendering any
> language independent of what the platform supports. And if I was working
> on something that relied on text rendering as its
True, if you are able/willing to supply a text renderer with your app
surely there's nothing in devices that would prevent it from rendering any
language independent of what the platform supports. And if I was working
on something that relied on text rendering as its core feature (say an
old-style
Thanks, that's good info. The reason I didn't check the source in this
case is, first, with min sdk of 7 that's a lot of source to check ;-) , and
second that this whole issue is fairly peripheral to our app.
I'm wondering if I can be reasonably sure that this code (or an equivalent)
runs in a ma
Thanks Piren. Alright, it's true that "Languages & input" might not show
everything the device is capable of. I'm fine with that though. My
highest priority concern is to avoid that a user sets the language to
something that the device can *not* handle. To ensure that, I'll gladly
skip exposing
latimerius wrote:
> Thanks for the reply. To explain a bit further: the reason I'm trying to
> get something similar to what the user sees in "Language & input" is, I
> just consider it unlikely that a device would offer a language that's it's
> not capable to handle, or that it would *not* of
Settings app:
https://android.googlesource.com/platform/packages/apps/Settings/+/refs/heads/master/src/com/android/settings/LocalePicker.java
Uses this:
https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/core/java/com/android/internal/app/LocalePicker.java
It's basica
Your reasoning is sound, but you're barking at the wrong tree... What shows
in Language & Input can be summed up to "This is what the company that made
the specific ROM you're using wanted the users to see when they use the
device", which has little affect on your app. Any language that shows
t
Thanks for the reply. To explain a bit further: the reason I'm trying to
get something similar to what the user sees in "Language & input" is, I
just consider it unlikely that a device would offer a language that's it's
not capable to handle, or that it would *not* offer a language it *can*
handle
I think you're confusing several different things the "Language and
Input" list that you're trying to fit isn't the same as the supported
locales ... This is just a list of languages the specific OS interface has
special versions for (i.e, the entire device UI will change). This is
localiza
13 matches
Mail list logo