>>>>> "Juliusz" == Juliusz Chroboczek <[EMAIL PROTECTED]> writes:
Juliusz> I may be mistaken, but it was my understanding that both
Juliusz> NTFS and VFAT ``long filenames'' use UTF-16.
This may be true in sane locales, but VFAT commonly uses Shift JIS in
Japan. AFAIK NTFS uses UTF-16, though.
>> I'd say that unix systems do it right
Juliusz> {-# OPTIONS -fadvocacy #-}
Juliusz> I'd argue that both models (Unix's and Windows') are
Juliusz> broken.
+1
Juliusz> Unix breaks property (2) (a file called ``e-circumflex''
Juliusz> under a French locale will be called ``e-ogonek'' under a
Juliusz> Polish one).
It's even worse than that. Some software validates the filename, so
if you have an encoding with reserved (ie, unused) codes (eg, ISO
Hebrew and some of the more arcane ISO Latin CCSes) you may have to
change locale to access the file.
Mac OS X does this, for example. Of course, in Mac OS X the only
valid encoding is UTF-8, so the worst that should happen is that the
create fails. With robust software you shouldn't lose any data, but
it's annoying.
Juliusz> So you need to move to a model where all locales use the
Juliusz> same character encoding.
Agreed, but as long as legacy CCSes are in use, there will still be
problems.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
