Re: And now for something completely different... etch!
-----BEGIN PGP SIGNED MESSAGE-----
md@Linux.IT (Marco d'Itri) writes:
> On Jun 08, Josselin Mouette <firstname.lastname@example.org> wrote:
>> As we have hundreds of broken packages assuming e.g. that the filenames
>> on disk are encoded in the current locale's character set, the only way
>> to make them interact properly with other applications is to set a
> Wrong. The problem is packages which need to interact with text files,
> mail and usenet messages generated by broken software, and for which
> assuming UTF-8 would be totally wrong.
This is completely orthogonal to making UTF-8 the default locale
The transition will in no way affect your need to use an old-fashioned
8-bit locale codeset if you need to do that. I fully expect that many
people will do exactly this for years to come, and the changing of the
*default* will not prevent this.
Please bear in mind that this is a change we need to make, which most
of the major commercial distributions did over a year ago, if not
before. Have you tried installing a recent SuSE or RedHat to check
this? When I checked late last year, all locales were UTF-8 by
default. We should have done this long before sarge was released.
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
-----END PGP SIGNATURE-----