On Mon, Mar 18, 2002 at 04:29:52PM +0000, Philip Blundell wrote: > On Mon, 2002-03-18 at 16:28, Matt Kraai wrote: > > On Mon, Mar 18, 2002 at 04:14:01PM +0000, Philip Blundell wrote: > > > On Mon, 2002-03-18 at 16:02, Matt Kraai wrote: > > > > When I test these settings on my installed system, it appears > > > > that Perl is unhappy with the `@utf-8' part of LC_CTYPE. Is > > > > this a valid locale, or are the boot-floppies blowing smoke? > > > > > > It is a valid locale, but only while you are running in the installation > > > root filesystem. After reboot, or if you chroot somewhere else, it will > > > stop being valid. I suspect that debootstrap may be running afoul of > > > the latter by chrooting into /target in order to configure these > > > packages. > > > > What is the advantage over `C'? Why is it only valid on the > > installation root filesystem? > > "C" uses the ASCII character set, not UTF-8. By definition, a locale is > only valid if it is present in /usr/lib/locale. The files for C@utf-8 > are created by rootdisk.sh and only exist in that one filesystem.
According to the LI18NUX2000 SPEC, with Amendament 3 [sic], UTF-8 coded character set should be usable under the `C' locale. If we remove the `@utf-8', does something actually break? Matt
msg17587/pgp00000.pgp
Description: PGP signature
