Bug with 21.5.16: cannot use UTF-8 encoded file names.

[Stephen J. Turnbull]

>>>>> "Mike" == Mike FABIAN <mfabian at suse.de> writes:

    Mike> I tried

    Mike>     xemacs -q -vanilla

    Mike> (running in ja_JP.UTF-8) and then tried to use files with
    Mike> UTF-8 encoded names, it didn't work. Then I executed

I don't think 21.5 knows how to deal with environment settings
properly yet.

[code omitted]

    Mike> in the *scratch* buffer, and tried again -> it didn't change
    Mike> anything, it still didn't work.

Unfortunately, there are a million different ways to use coding
systems.  Of course, for a Makefile, file name encodings and file
content encodings had better be the same, but in other cases, where
the system is unibyte but you want UTF-8 files, you really want them
separate.  XEmacs 21.5 provides a couple _dozen_ different places
where you can tweak coding systems.  I think file names are currently
initialized to X Compound Text except on Windows.  I forget where
initializations are documented, but lisp/coding.el has a lot of the
interface.  You probably want to set `file-name-coding-system'.

This is a major reason why 21.5 cannot be considered ready for prime
time even when the code is actually fairly stable: all of these
details need to be worked out still.

-- 
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.