David Starner wrote on 2001-02-05 16:48 UTC:
> On Mon, Feb 05, 2001 at 11:56:41AM +0000, Markus Kuhn wrote:
> > The best solution is to assume that the file names are in the
> > locale-specific multi-byte encoding. Simply use mbrtowc and wcrtomb to
> > convert between Unicode and the locale-dependent multi-byte encoding
> > used in file names and text files if the ISO C 99 symbol
> > __STDC_ISO_10646__ is defined (which guarantees that wchar_t = UCS). On
> > Linux, this has been the case since glibc 2.2.
>
> Could there be a LC_FSCHARSET?
Please not. Let's get rid of encoding aspects of locales as soon as
possible, not add more mechanics that would only be needed temporarily.
If your software can handle UTF-8 filenames, it can most likely also
handle UTF-8 on its other ports.
> I tend to run around in Latin-1 locales with UTF-8 filenames.
Sounds tedious. I'd rather recommend either Latin-1 locales with Latin-1
filenames or UTF-8 locales with UTF-8 filenames.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
