Date: Sun, 1 Feb 2004 14:49:13 +0200 From: Ruslan Ermilov <ru@FreeBSD.ORG> To: Andrey Chernov <ache@nagual.pp.ru> Cc: i18n@FreeBSD.ORG Subject: Re: Documenting composite LC_ALL locale, anyone? Message-ID: <20040201124913.GB59402@FreeBSD.org.ua> In-Reply-To: <20040201123128.GA59402@FreeBSD.org.ua> References: <200401312329.i0VNTKCH067740@repoman.freebsd.org> <20040201093646.GD57540@FreeBSD.org.ua> <20040201094001.GA40180@nagual.pp.ru> <20040201104146.GF57540@FreeBSD.org.ua> <20040201120050.GA41545@nagual.pp.ru> <20040201120805.GA41753@nagual.pp.ru> <20040201123128.GA59402@FreeBSD.org.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
--8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable One option to deal with this complex case (LC_ALL, composite locale, and when some of the components start with a `/') would be to replace each single slash with two adjacent slashes, so an argument of `/pathto/localedef/output' would become `//pathto//localedef//output'. Then double slashes in the input would represent a single slash, and single shash would represent a component separator. Unfortunately, POSIX-200x is silent on this case while requiring that the output of ``setlocale(LC_ALL, NULL)'' should be such that when it's fed back to ``setlocale(LC_ALL, ...)'' it should restore all of the locale components. Perhaps we should seek for some clarifications in the Austin Group? ;) Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAHPXJUkv4P6juNwoRAt4vAJ0aflgLhZ/1vNYfOueUQq0jEWZoSACfeD4E giF9cKztKRrTPerxWxLrsnU= =Rzh1 -----END PGP SIGNATURE----- --8GpibOaaTibBMecb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040201124913.GB59402>