They do ship with font support for most languages. Note that this is complicated though because for example Chinese vs. Japanese fonts have different glyphs for the same Unicode code point.
On Thu, Jun 9, 2011 at 8:33 PM, Mark Carter <mjc1...@googlemail.com> wrote: > Are we talking about two different things here? Font support and locale (?) > support? > > I can understand why a US-only device would not need to ship with support > for locales like Japanese and Thai, but there is a stronger argument to > include Japanese and Thai fonts (space permitting) because they are useful > to translator apps and the browser etc. > > Is there any way to programmatically check whether a unicode char is > displayable? A negative check would allow us to then fall back on a ttf file > in the assets (which I think is a better way than just forcing the assets > file in the first place). > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
