Summary: | 'Verify written data' always fails when filenames contain non-ASCII characters | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Michał Kosmulski <michal> |
Component: | general | Assignee: | Sebastian Trueg <trueg> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Michał Kosmulski
2004-10-08 18:41:43 UTC
Additional info: 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. 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 project verification. The result is: no charset problems anymore. BUG: 90974 BUG: 84544 BUG: 90977 BUG: 105649 BUG: 113052 BUG: 83315 BUG: 80593 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 |