Re: And now for something completely different... etch!
-----BEGIN PGP SIGNED MESSAGE-----
Javier Fernández-Sanguino Peña <firstname.lastname@example.org> writes:
> Feel free to add some new items or add (hopefully new) information to the
> ones I list below:
[Transition to UTF-8 locales]
- - The locale codeset should be UTF-8 for all new installs by default.
- - Existing installations should be unaffected, but it might be nice to
offer to generate the equivalent UTF-8 locales for the locales in use.
- - When UTF-8 is the default locale, it shouldn't need a .UTF-8 suffix,
e.g. en_GB will be UTF-8, and en_GB.ISO-8859-1 will be Latin-1 (the
opposite way round to the current situation which creates
en_GB.UTF-8 and en_GB [Latin-1]).
This change has (as far as I can tell) been done already by most major
commercial distributions (e.g. SuSE, RedHat). The actual mechanics of
the transition should be fairly straightforward, since UTF-8 locales
are already supported, this is simply switching the defaults in the
locales package. This won't affect existing installs, so breakage
should be none to minimal.
At a later point, we should also look into recoding our documentation
into UTF-8. While reviewing RC bugs for sarge, I found that the
DocBook toolchain is quite broken WRT text encoding support. It
doesn't put the encoding in the generated HTML, which nowadays is not
acceptable. See gnupg-doc for examples.
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-----