Re: Limping along with UTF-8

Steven> I also want all my files to be opened and saved as UTF-8. (set-coding-priority-list '(utf-8 no-conversion)) I'm assuming from what you've said before that you REALLY want ALL files opened as UTF-8. The above means that as far as Mule is concerned if it's not UTF-8, it's binary. If not, (set-coding-priority-list '(utf-8)) Mule will try UTF-8 first, and if that doesn't make sense, various ISO-2022, Shift JIS, Big 5, etc. Steven> I don't know the significance of this, but there is at Steven> least one character which is UFT-32 which I would like to Steven> be able to use. Does that mess up everything? Probably. I suspect Mule-UCS will "corrupt" any character that is not known to it as a regular Mule character. Emacs does not have a standard way to represent such characters. AFAIK UTF-32 (by which I presume you mean 4-octet UTF-8) is not a problem as such (XEmacs can handle up to 31-bit integers, so full UCS-4 is not OK, but UTF-32 is). So, the solution is simple, in principle: create a private charset, map it to fonts, and teach Mule-UCS about it. (I suspect this solution is also general in the sense that we could create such a charset on the fly and just stick the characters in there, adding new ones to the charset and to the Mule-UCS database as we detect them.) How do you, uh, "normally" access this character? (This is the first time I've actually heard of a case where UTF-32 is needed!) Do you have fonts and an input method? -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py