On Sat, 2 Mar 2002, Markus Kuhn wrote: > Radovan Garabik wrote on 2002-03-01 22:52 UTC: > > 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?). > > If I'm not mistaken, joliet uses UCS-2 or UTF-16.
That's right. > Make sure that you have a *very* recent version of mkisofs, as older > ones do not know about UTF-8 (which has to be converted my mkisofs for > joliet, but not for RockRidge). Which version of mkisofs supports UTF-8? Last time I checked (which was just a month ago), it didn't support any of multibyte encodings (including UTF-8. there's a Japanese patch to support multibyte encodings for CJK users) and the newest one I can find at cdrecord home page (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/mkisofs.html) doesn't seem to support UTF-8, yet let alone other multibyte encodings. I made a _quick and dirty_ patch to get mkisofs to use iconv(3) instead of its not-so-elegant (for single byte encoding only) built-in converter because I needed to burn Joliet CDs with filenames in EUC-KR. I sent the author my patch (again, it's a quick and dirty patch and can't be used on platforms other than Linux as it is, but it could give him an idea). He didn't appear much interested in it. He asked me if 'iconv(3)' is available on platforms other than Solaris and I wrote him that Glibc has had iconv(3) for over two years and a stand-alone libiconv is available for *BSD or other Unix w/o iconv(3). I haven't heard since. Jungshik Shin -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
