Bug#99933: third attempt at more comprehensive unicode policy

[barbier@linuxfr.org (Denis Barbier)]

On Wed, Jan 15, 2003 at 09:34:00PM -0500, Colin Walters wrote:
[...]
> I am a bit wary about involving them; it doesn't seem to quite fit in
> with their charter.  However, I just noticed the 'Open
> Internationalization Initiative', which is part of the same Free
> Standards Group umbrella organization that the LSB is.  Stuff like this
> does seem like it would fit in with their work; charset issues and
> internationalization do go hand in hand.
> 
> However, I just looked through the most recent release of their
> standard, and they appear to be silent on all the issues under debate
> here; what charset to use for filenames, how to handle filenames not in
> UTF-8, etc.

Excerpt from http://www.openi18n.org/docs/html/LI18NUX-2000-amd4.htm

      portable filename character set

   The set of characters from which portable filenames are constructed.
   For a filename to be portable across implementations conforming to
   this specification set and the ISO POSIX-1 standard, it must consist
   only of the following characters:

   A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

   a b c d e f g h i j k l m n o p q r s t u v w x y z

   0 1 2 3 4 5 6 7 8 9 . _ -

   The last three characters are the period, underscore and hyphen
   characters, respectively. The hyphen must not be used as the first
   character of a portable filename. Upper- and lower-case letters retain
   their unique identities between conforming implementations. In the
   case of a portable pathname, the slash character may also be used.

Denis