On 2002-03-01 23:52 Radovan Garabik wrote:
> Greetings
> I am going to burn some CD's with filenames in UTF-8, and before
> doing so, I would like to ask if there are any known problems. I do
> not expect them with RockRidge extension, but a big unknown is
> interoperability with different versions of Windows (what charset is
> default for joliet extension?). Unfortunately, I have neither RW
> media neither Windows readily available for testing
As you say, Rock Ridge have no problems with this -- this is the
recommended way to do it. When it comes to Joliet the problems begin to
pile up:
- Joliet use Unicode by default. Every character is represented in
UTF-16, so characters above U+FFFF can't be stored properly when
done the windows way.
- Maximum length of Joliet file names is 64 UTF-16 characters, so you
quickly run into the wall here, especially if you have many long
UTF-8 sequences. If mkisofs(8) complains about "foo and bar have
the same Joliet name", this is the case.
- AFAIK mkisofs does not convert UTF-8 sequences to UTF-16 during
creation of the image, so windows believes the UTF-8 sequences is
real text, and you will have a hard time getting rid of them in
applications.
After experiencing this again and again, I'm really frustrated of the
crippled design of Joliet, so most of the time I drop the whole Joliet
support when I have long filenames or lots of UTF-8 filenames. Things
would have worked so well if there was a way of forcing windows to use
the TRANS.TBL file which is represented in every directory on the disc.
I'm not into windows stuff, but I guess there should be a way to do
this with some .dll magic or what?
�yvind
+===================================================================+
| OpenPGP: 0x629022EB 2002-02-24 �yvind A. Holm <[EMAIL PROTECTED]> |
| Fingerprint: DBE9 8D44 67F7 42AC 2CA1 7651 724E 9D53 6290 22EB |
+================== ☮, ♥ and Linux. ==================+
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
