Re: base-config localisation
Hi,
At 05 Feb 2002 10:27:12 +0900,
Olaf Meeuwissen wrote:
> > Take in account that server software (ftp servers, mailing lists, web
> > servers) cannot usually take in account localisation because it is not
> > provided by the client software (for web servers there is content
> > negotiation however). Thus, it has to be customised on a per-system basis.
>
> What is wrong with ftp servers and mailing lists (running as what?
> root, ftp, ...) processing /etc/environment? If they are properly
> i18n-ized, they should already heed a LANG setting anyway.
I have no idea how servers can be internationalized in such a way.
Servers' i18n means that these servers have to work well with clients'
locale setting. Thus, it is impossible for servers to have one
fixed locale.
Anyway, in ftp server, completely no i18n is needed, because there
are not way to send locale information from clients to servers.
In this context, "translation", i.e., LC_MESSAGES, is a only part
of i18n, and a relatively small part of i18n.
On the other hand, LC_CTYPE is the most important part of i18n,
because this is a basis of all other part of i18n and even a basis
for all text data.
LANG=C in system-wide setting might have an aim to stress that
usage of non-ASCII characters (like Latin-1, EUC-JP, and UTF-8)
is invalid in system-wide files, which is a matter of course though.
---
Tomohiro KUBOTA <kubota@debian.org>
http://www.debian.or.jp/~kubota/
"Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/
Reply to: