Re: And now for something completely different... etch!
-----BEGIN PGP SIGNED MESSAGE-----
Adrian von Bidder <firstname.lastname@example.org> writes:
> On Tuesday 07 June 2005 23.32, Roger Leigh wrote:
>> Frans Pop <email@example.com> writes:
>> > On Tuesday 07 June 2005 23:02, Roger Leigh wrote:
>> >> Existing installs are already configured with debconf. Their
>> >> /etc/locale.gen will not be touched.
>> >> If you do dpkg-reconfigure locales, then users could have the locale
>> >> switch to UTF-8 if they so choose.
>> > AFAIK locales are automatically regenerated when the locales package is
>> > upgraded, so this _would_ effect every existing install directly on
>> > upgrade to the new release.
>> locale-gen is run, but /etc/locale.gen is not necessarily altered. If
>> you don't change it, it will regenerate the same locales you already
> But 'the same locale I already have' would probably mean 'the locale with
> the name of the locale I previously had' which has now suddenly changed its
This would be safe, since the locale codeset is part of the name.
When the current locale selections are merged with i18n/SUPPORTED, it
wouldn't change anything behind your back. But this is probably the
wrong approach, as others have said.
I've since made a patch, and filed this as bug #312927. I'd
appreciate any comments. It's a trivial and (I hope!)
non-controversial change. It certainly won't affect the choices of or
the behaviour of the available locales; it rather just recommends that
UTF-8 locales be used unless the user has a good reason not to.
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-----