May 23, 2013
10:06 a.m.
On 23.05.2013 03:59, Yoshiki Ohshima wrote:
For Pharo, I'd guess so, too.
(I heard that the Japanese support is pretty much dropped in Pharo.)
--
If you mean using leadingChar to indicate WideStrings using non-unicode encoding, and Bitmapped fonts with multiple sets for non-latin1 ranges taking it into account when selecting glyph, then yes, it's pretty much been dropped. If you have a TrueType font with unicode -> japanese glyphs, it should still work though. Cheers, Henry