I have two machines running FC2. On those machines, I have no problems with emacs and Japanese text (hiragana, katakana, kanji). I can visit files containing Japanese text encoded in UTF-8; emacs autodetects UTF-8 encoding and displays the text properly. I can save buffers containing Japanese text using the utf-8 coding system. In short, on the FC2 machines, Japanese text in emacs just works. I just loaded FC3 on a third machine. On the FC3 machine, I can't get emacs Japanese text support working. If I visit a buffer containing Japanese text encoded in UTF-8, I just get a bunch of gibberish (backslash octal characters and empty boxes). I can paste Japanese text (copied from another application) into Emacs buffers, and it displays properly, but then if I attempt to save the buffer, I receive this message: > These default coding systems were tried: > utf-8 > However, none of them safely encodes the target text. > > Select one of the following safe coding systems: > euc-jp shift_jis iso-2022-jp iso-2022-jp-2 x-ctext > japanese-iso-7bit-1978-irv iso-2022-7bit raw-text emacs-mule > no-conversion iso-2022-7bit-lock-ss2 ctext-no-compositions > iso-2022-8bit-ss2 iso-2022-7bit-lock iso-2022-7bit-ss2 > tibetan-iso-8bit-with-esc thai-tis620-with-esc lao-with-esc > korean-iso-8bit-with-esc hebrew-iso-8bit-with-esc > greek-iso-8bit-with-esc iso-latin-9-with-esc iso-latin-8-with-esc > iso-latin-5-with-esc iso-latin-4-with-esc iso-latin-3-with-esc > iso-latin-2-with-esc iso-latin-1-with-esc > in-is13194-devanagari-with-esc cyrillic-iso-8bit-with-esc > chinese-iso-8bit-with-esc japanese-iso-8bit-with-esc I cannot see how this message can be correct, because UTF-8 encodes *everything*. Emacs Japanese text support worked just fine on FC2, but now it appears to be broken on FC3. All other FC3 applications I've used have worked just fine; it only seems to be emacs that is broken. Does anyone know what's going on and how to fix it? (I did an "Everything" install when I loaded my FC3 machine, so I am hoping that the problem is something simple, like I accidentally included some bogus "backwards-compatibility" package designed for Japanese text support in the days before UTF-8.) Thanks in advance for any pointers. -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA