From: Con K. <co...@ko...> - 2006-09-10 16:45:42
|
On Sunday 10 September 2006 14:13, Con Kolivas wrote: > On Sunday 10 September 2006 13:55, George Williams wrote: > > On Sat, 2006-09-09 at 03:56, Con Kolivas wrote: > > > When choosing the Japanese interpretation, every time I generate a font > > > it comes up with "bad encoding single byte character (161) for one of > > > the slots for double byte characters" and "there is a character (33088) > > > which cannot be encoded" and same for 57472 and then it repeats the 3 > > > messages a 2nd time. > > sjis.patch fixes it, thanks :) Followup question on a related note. When I have a japanese interpretation on a unicode BMP encoding, if I generate a font from that and then load the generated font it comes up as SJIS encoding. Starting with mikachan.ttf will do this for example (http://prdownloads.sourceforge.jp/mikachan/5513/mikachanfont-8.9.tar.bz2). Is this sjis encoding intentional? This happens only on "regular" sized japanese fonts. The ones with extra characters (like the "pro" fonts), or for example the opentype version of mikachan, (http://mikachan.sourceforge.jp/mikachan_o.lzh) comes up as unicode. Thanks -ck |