Re: Documenting composite LC_ALL locale, anyone?

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,
-- 
Ruslan Ermilov
FreeBSD committer
[email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAHPXJUkv4P6juNwoRAt4vAJ0aflgLhZ/1vNYfOueUQq0jEWZoSACfeD4E
giF9cKztKRrTPerxWxLrsnU=
=Rzh1
-----END PGP SIGNATURE-----