![]() |
2007-11-29
, 15:51
|
|
Posts: 772 |
Thanked: 183 times |
Joined on Jul 2005
@ Montclair, NJ (NYC suburbs)
|
#1
|
The Following User Says Thank You to RogerS For This Useful Post: | ||
![]() |
2007-11-29
, 15:55
|
Posts: 246 |
Thanked: 6 times |
Joined on Jul 2007
|
#2
|
![]() |
2007-11-29
, 16:00
|
|
Posts: 772 |
Thanked: 183 times |
Joined on Jul 2005
@ Montclair, NJ (NYC suburbs)
|
#3
|
![]() |
2007-11-29
, 23:07
|
Posts: 183 |
Thanked: 115 times |
Joined on Nov 2007
@ Seattle, WA
|
#4
|
Especially since you can't view Unicoded web-pages in those languages on a Nokia Internet Tablet.
The Following User Says Thank You to baksiidaa For This Useful Post: | ||
![]() |
2007-12-07
, 16:14
|
|
Posts: 772 |
Thanked: 183 times |
Joined on Jul 2005
@ Montclair, NJ (NYC suburbs)
|
#5
|
I'm pretty sure I do have full unicode support on my N800. I just created the folder .fonts in the user root and copied a unicode font file into it. The browser handles the complex text positioning just fine.
![]() |
2007-12-07
, 19:24
|
|
Posts: 772 |
Thanked: 183 times |
Joined on Jul 2005
@ Montclair, NJ (NYC suburbs)
|
#6
|
There are some very minor rendering problems for Thai, mainly having to do with proper positioning of tone marks and vowels that might have to be shifted up or left slightly.It sounds to me like Thai is a lucky language from a Unicode-hobbled Internet Tablet perspective -- no special support, but no special support needed.
The canonical example for ordering is "ek" (entry) vs. "ke" (sound). The vowel appears before the consonant for all Indic-derived SEA scripts, but is entered after the consonant for Burmese and Khmer.
Khmer and Burmese are unusual (in Western terms) because the interchange standard requires complex rendering in order to be comprehensible.
In contrast, English and Thai can be shown reasonably (albeit with occasional awkward character positioning) with purely bitmapped glyphs.