Re: Mule, win32 native, current cvs
"Stephen J. Turnbull" <[email protected]>
| Newsgroups | gmane.emacs.xemacs.windows,gmane.emacs.xemacs.beta |
|---|---|
| Organization | The XEmacs Project |
| Message-ID | <[email protected]> |
>>>>> "Ben" == Ben Wing <[email protected]> writes: Ben> but this doesn't prove anything. the question is, where did Ben> the e-acute come from? if this is from unicode conversion, Ben> maybe the language list is messed up. My guess is that it's the language list, but it could be anywhere because of how screwed up Mule has historically been about handling environments. I would start by pruning the list of character sets loaded by default. chinese-sisheng is presumably of mostly historical interest now. Only linguists and Chinese educators could possibly be interested in it, and they presumably would prefer to use Unicode or a Chinese character set that includes hanzi. IPA is another that should go, if it has a non-Unicode encoding. The CNS coding systems are basically unused. Really the only languages that should have multiple non-Unicode coding systems loaded by default are Japanese ("hello, foot, meet my friend bullet") and Russian (KOI8 is a Cold War relic, I guess, but unlike ISO 2022 and EUC the ISO standard is basically not accepted in Cyrillic countries). Ben> stephen, any insights? you're the latin-unity guy. I didn't know anything about chinese-sisheng; latin-unity has nothing to do with that. ... Hm, still doesn't, that's not a latin alphabet, it's a phonetic alphabet for Chinese that happens to include some latin characters. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.