Version: 0.11.17 (using KDE KDE 3.3.0)
Compiler: gcc 3.3.4
I record my CDs with both Joliet and RockRidge extensions turned on, so I expect that all filenames be written to the disc using Unicode characters. My system uses a UTF-8 locale. When there is a file containing non-ASCII characters (e.g. Polish diacritics) in its name and 'Verify written data' is enabled, verifying the recorded disc always fails, even if a manual md5sum check confirms that the disc was recorded correctly.
I use supermount (supermount-ng.sourceforge.net) for mounting the CD-burner, the line in /etc/fstab is:
none /mnt/cdrom supermount fs=iso9660,dev=/dev/cdrom,--,auto,ro,utf8 0 0
but I also tested with a normal mount:
/dev/cdrom /mnt/cdrom iso9660 defaults,users,noauto,ro,utf8 0 0
and got the same results. Verifying fails, even though I can manually check that all files were recorded correctly, with the message 'Could not find XYZ', where XYZ is the name of one of the files whose names contain non-ASCII characters. I burn with all 'compatibility' options ('allow 31 char names' etc.) disabled.
sounds like a dup of bug 83315
SVN commit 487359 by trueg:
Copied iso9660 filename generation code from mkisofs. With it K3b is able
to determine the iso9660 names generated by mkisofs and use them for data
The result is: no charset problems anymore.
M +620 -39 projects/datacd/k3bdatadoc.cpp
M +2 -0 projects/datacd/k3bdatadoc.h
M +11 -0 projects/datacd/k3bdataitem.cpp
M +15 -3 projects/datacd/k3bdataitem.h
M +1 -2 projects/datacd/k3bdataverifyingjob.cpp
M +109 -29 tools/k3biso9660.cpp
M +29 -2 tools/k3biso9660.h