>I'm still not certain of the exact cause of, for example, EUC-JP and >Shift-JIS ending up in ID3V2 tags.
It may be similar to the problems with the dict spec. The RFC for dict servers dictates that UTF-8 shall be used. A dict file provided by the author of the RFC used with the server by the same author sends ISO-8859-1. Since the usual dict server (from that author) doesn't support multibyte encodings, and the usual dict client (from the same author) doesn't recode anything, everyone uses their own encodings and forgets about the standard or any hope of mixing dictionaries of different languages. I'd guess few programs that use ID3V2 take any note of the encoding, just passing through without recoding. So for it to work right on one system, people use the local encoding. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
