On 3 Nov 2001, H. Peter Anvin wrote: > Followup to: <[EMAIL PROTECTED]> > By author: Nerijus Baliunas <[EMAIL PROTECTED]> > In newsgroup: linux.utf8 > > > > HPA> > > HPA> In practice, as all of this painfully illustrates, is that multiple > > HPA> encodings in anything but an isolated environment is ultimately > > HPA> futile. Whereas data in a lot of contexts can be labelled, stuff that > > HPA> is "around the system in general" -- may it be usernames, filenames, > > HPA> /etc/passwd, etc, are ultimately have to be encoded in the encoding > > HPA> specified by the system default locale, and the goal is for that to > > HPA> become UTF-8. > > > > Excuse me, what a mess that would create! How would you know which encoding > > /etc/passwd is in? What if you have both Japanese and Russian users on > > your system? UTF-8 is the only candidate. You can use iconv to convert > > user's input to UTF-8. > > > > I told you... it has to be in the *system default* character > set/locale. In practice, UTF-8 is the only choice for multilingual > support, but there is a fair number of systems which currently use > ISO-8859-1.
What is the *system default character set/locale*? where is it defined? -- Behdad 13 Aban 1380, 2001 Nov 4 [Finger for Geek Code] -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
