| Summary: | Verifycation fails when burning files with international characters | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Oldřich Jedlička <oldium.pro> |
| Component: | general | Assignee: | Sebastian Trueg <trueg> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | akontsevich, jlp |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Oldřich Jedlička
2004-06-13 19:54:35 UTC
I must confirm this bug. I have the ISO-8859-2 file system with internationalized file names (žšč...), too, and after burning on-the-fly or with intermediate image the verifying fails with "Could not find file XYZ" error message. I tested it on my CD-RW medium. I've also had this problem, but with an iso-8859-1 filesystem. I think the problem is that K3B always interprets filenames in the encoding in which it was started (UTF-8 in my case). k3b-0.11.18 and it seems to me I have the same bug... Same problem here. I'm using 0.11.22 and it always fails with non-ASCII names. My system encoding is UTF-8, and I'm always burning Rockridge-only CDs. What's interesting is that, in the error message, the filename that cannot be found is shown correctly. When I have a look at the CD (in k3b itself) the file is there, and it's shown correctly. Here with Suse 9.3 Kde 3.4.2 and k3b 0.12.3 the same. In my case its german umlaute that cause the problem. Matthuas since i remember k3b i remember unable to vrify non "standard" chars. ver 0.12.2 . i think the problem is, k3b is converting the chars when reading source only on verification stage only. i use only rockridge extension while allowing 103 chars joliet filenames and untranslated iso9660 filenames. iso level 2. and i do not force input charset. I can conform that when burning with german umlauts the verification fails, but the files are present on the CD. Please fix this as its very important IMHO I have the same problem here with special Slovenian characters and ISO-8859-2 charset. K3b 0.12.4a on KDE 3.4.2. When can we expect to see the fix? I already lost my faith and hope. I thought that verification is very important feature, but maybe I was wrong. probably after I finished my diploma thesis... It still fails with 0.12.4a... which esentially means that I can as well turn of testing because it fails always! Matthias that's because I did not fix it yet. This is a bigger thing and I don't have the time right now... A YES/NO dialog asking for continue should fix temporarily this problem :) A simple YES/NO dialog asking for continue should temporarily fix this problem. At least it wont burn bad disk. how? what is k3b supposed to ask and based on what check? *** Bug 117809 has been marked as a duplicate of this bug. *** 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 Great :-) Thanks a lot. I'm looking forward to new release to try it :-) Thanks! Turning on verification again from the next release! Hurrah, Hurray!!! Thank you VERY VERY much!!! :) And how international caracters will look in Windows now? Correctly? On Saturday 10 December 2005 20:45, GladAlex wrote:
> And how international caracters will look in Windows now? Correctly?
That should not have changed. sorry.
> > And how international caracters will look in Windows now? Correctly?
> That should not have changed. sorry.
Why? What about the future? Why international characters in CD recorded in
windows look correctly in linux, but not vice versa?
probably updating mkisofs fixes the problem. It did here. mkisofs 2.1 works. Verifycation STILL fails!!! hmm... not good. which locale? Could you also give me some filenames (that fail in verification) so I can recreate the problem here. It is difficult to catch it, sometimes it works, sometimes not and I haven't found a reproducible setup yet. However it might be related that when running k3b from within a directory containing international characters in its name, the following error messages appear: [hajma@localhost Písně Středozemě]$ LANGUAGE=C k3b --nofork shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory I'm using cs_CZ (czech) locale with iso-8859-2 K3b 1.0 will fix the problem once and for all. |