On Wed, Sep 11, 2002 at 01:20:25PM +0900, Junichi Uekawa wrote: > > One concern is that I've heard that UTF-8 is really not all there for > > Japanese (Chinese?). I'm told that doing a round-trip conversion from > > Shift-JIS to UTF-8 has issues. I don't know if translators can just avoid > > those problem encodnings and write ja.po files that are already in UTF-8. > > ja.po files are in EUC-JP.
Well, they *can* be UTF-8. > Wouldn't just having "Description-ll_LL.ENCODING:" fields work fine ? > I've got a feeling that it's doable. > > I can think of ways to implement that at least in C. What's wrong with using UTF-8 for Japanese? Having multiple encodings in a single text file sucks. I'm aware of the problems described at http://www.debian.or.jp/~kubota/unicode-symbols.html but they all only seem to be related to the slightly varying vendor tables, and not a problem when iconv is used consistently. What other problems are there that are severe enough to need this? -- Glenn Maynard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
