I can see doing that for the Kanji, which look similar enough, but
what about the katakana and hiragana in Japanese text? These
characters do not exist in Chinese, and the Japanese would be really
unreadable if they were mapped to the kanji they were originally
derived from.
On Jun 9, 10:30 pm,
On Wed, Jun 15, 2011 at 5:08 AM, Indicator Veritatis mej1...@yahoo.com wrote:
I can see doing that for the Kanji, which look similar enough, but
what about the katakana and hiragana in Japanese text? These
characters do not exist in Chinese, and the Japanese would be really
unreadable if they
The problem with languages (locales) seems to be more related to the
wireless
company than the phone makers. I recently taught a course on
developing
Android apps, and there were several different phones used by myself
and my
students. Those who had ATT phones, for example, seemed to have a
lot
The initial Xoom was a US-only device, so the other languages were not
needed. Since that was the first release of Android 3.0, generating all of
the translations would have delayed the product for stuff it didn't need.
It is just going to be a fact of life that different devices will ship with
Xoom is absolutely not a US only device. You can buy it in Singapore
where I live from official channels. Also, 3.1 still only got the 3
languages which makes your 'reference Honeycomb device pretty
useless for localization testing -
On Jun 10, 2:28 am, Dianne Hackborn hack...@android.com
As I tried to indicate, I only know about the the initial device which was
in fact US only. Further software updates to that device are also US only.
I don't know about devices being sold in other countries.
On Thu, Jun 9, 2011 at 5:19 PM, Zsolt Vasvari zvasv...@gmail.com wrote:
Xoom is
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
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
On Fri, Jun 10, 2011 at 1:08 PM, Dianne Hackborn hack...@android.com wrote:
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.
How is this handled in
Currently at build time one of them must be selected.
On Thu, Jun 9, 2011 at 9:24 PM, Nikolay Elenkov
nikolay.elen...@gmail.comwrote:
On Fri, Jun 10, 2011 at 1:08 PM, Dianne Hackborn hack...@android.com
wrote:
They do ship with font support for most languages. Note that this is
On Fri, Jun 10, 2011 at 1:32 PM, Dianne Hackborn hack...@android.com wrote:
Currently at build time one of them must be selected.
Any plans to change this to something more flexible?
BTW, it seems Chinese is the default, because all non-Japanese phones (don't
know about tables), display
2)I guess there is no guarantee. To be certain of the font
availability, considering .ttf file size, it should be better for you
to include desired font inside /assets directory, and then load it
with something like this:
public void setFont(TextView in){
Typeface font =
On 8 Giu, 10:28, Shine shineange...@gmail.com wrote:
2)I guess there is no guarantee. To be certain of the font
availability, considering .ttf file size, it should be better for you
to include desired font inside /assets directory, and then load it
with something like this:
ok, but there is
Here are the fonts in the android source.
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=tree;f=data/fonts;h=b63895f0105adc2a62f648293b14aa89cc64e3f2;hb=HEAD
These are listed in the makefile
DroidSans.ttf
DroidSans-Bold.ttf
DroidSansArabic.ttf
yes those fonts are for the last platform, I guess Gingerbread that
provides an extended language support.
However I noticed something strange... On my Nexus S there are a lot
of languages supported selectable, on the other hand on my Nexus One
(always 2.3.4) there are only a subset of those.
I
Nexus One has a smaller partition for the system image, so can't fit every
possible thing. New translations were added to the platform after the
initial Nexus One release, but those new translations are not included on N1
due to the limited space.
On Wed, Jun 8, 2011 at 7:41 AM, Paolo
But even my Xoom only includes 3 languages so it's almost useless for
testing translations -
On Jun 9, 12:04 am, Dianne Hackborn hack...@android.com wrote:
Nexus One has a smaller partition for the system image, so can't fit every
possible thing. New translations were added to the platform
That's awful. My HTC Magic which came out in 2009 supports ~40
languages/varieties.
--
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,
18 matches
Mail list logo
