After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546592 - Filenames on Cd shortend [Windows 2000 Explorer view] or changed through brasero
Filenames on Cd shortend [Windows 2000 Explorer view] or changed through brasero
Status: RESOLVED DUPLICATE of bug 589919
Product: brasero
Classification: Applications
Component: general
0.7.1
Other All
: Normal normal
: 0.8
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-08-06 13:42 UTC by BS-Direkt
Modified: 2011-10-20 17:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description BS-Direkt 2008-08-06 13:42:55 UTC
Please describe the problem:
1. Filenames changed on burned CD: If i burn some files from a fat32 and some  files from  a ext3 partition, then space characters in filenames are transformed  to "%20"-Strings . The filenames look something unreadable in nautilus. All this happend when i used ubuntu 8.04 and burned simple data-CDs with brasero.

2. Other brasero-problem with burning simple data cds: I can burn files from ext3 or fat32 partitions separately. But the cds with content from ext3-partitions show an other strange behaviour:  This is only visible with the windows explorer [i use ubuntu 8.04 and windows 2000 on my pc]. The windows explorer shows shortend 8.3-filenames like DOS. Nautilus correctly shows the "longer" filenames ... But the feature "increase compatibility with windows systems" is switched on. 

 Is there something wrong with the readability of the cd format?

Best regards,
Bernhard

Steps to reproduce:
1. see above!
2. do  the same!
3. 


Actual results:
I happens again, what else?

Expected results:


Does this happen every time?
perhaps. not checked! I don't burn thousands of cds.

Other information:
no.
Comment 1 David King 2011-10-20 17:18:20 UTC

*** This bug has been marked as a duplicate of bug 589919 ***