GNOME Bugzilla – Bug 589919
File names truncated when disc contents viewed in Windows
Last modified: 2018-09-21 16:37:39 UTC
Please describe the problem: File names on data discs burned using Brasero are truncated to DOS-style 8.3 format and capitalized when viewed on a computer running Windows XP. However, when the contents are viewed on Linux, long mixed-case file names display correctly. For example "LongMixedCaseFileName.html" becomes "LONGMIXE.HTM", but only when viewed on Windows. Steps to reproduce: 1. Open Brasero Disc Burner; choose "Data Project"; add any files with long or mixed-case file names. 2. Click burn. 3. View the disc contents in Windows XP. Actual results: File names are truncated to 8.3 format (only when viewed on Windows). Expected results: File names displayed in full on Windows (as they are on Linux). Does this happen every time? Yes. Other information: The behaviour is consistent whether the "maximise Windows compatibility" box is ticked or not. K3b running on the same machine does *not* exhibit this behaviour; discs burned using K3b show correct file names on all operating systems.
You need to use the nonstandard Joliet format or the standard UDF format in order to make MS-Win see the filenames correctly.
How do you enable these formats in Brasero? I do not seem to be able to find the options.
FWD from: https://bugs.launchpad.net/brasero/+bug/416731 Using Ubuntu 9.04 x64 and Brasero 2.26.1 A quick description of the bug is: Ubuntu can read long file name in a data DVD written by a Windows software. The opposite is not always true. Brasero writes something in the DVD so that Windows only see capitalized 8.3 folder / file name. But when read under Ubuntu, all the long file names are intact. It is not a long file name problem. Brasero can write long file name which is Windows compatible (meaning can be read by Windows and the long file name appears as the original name). Example (without quotes) "Ubuntu_0-94 - 64 bits Version.txt". However, when the folder / file name is longer than 64 chars or may be has symbol. Example (without quotes) "Ubuntu_0-94 - 64 bits Version (April 2009).txt" Then when the Burn button is clicked, Brasero UNCHECK the "Increase compatibility with Windows System" box. If you continue to burn the CD/DVD then the file / folder is transformed into captialized name and truncaeted to 8.3 format. Example: UBUNT_01.TXT. However if the CD/DVD is read using Ubuntu then the file name appears as its original name. A file has a name, the file is written in a DVD. The DVD doesn't know which OS is going to read it. When Windows writes that file / folder name in the DVD, Ubuntu can read it. When Brasero writes the same file name in the DVD, Windows can no longer read it. There is no waring on Ubuntu system that states "Ubuntu can only read data DVD written specifically for Ubuntu". Therefore I assume that the DVD format must be universal and compatible between Windows & Ubuntu. To reproduce this bug: 1. Create folder named: "Test Brasero Long File name (Aug.2009)" 2. Copy any binary file into this folder and rename it to: "01 - Brasero [2.26.1] and Ubuntu Linux 9.04 version 64 bits.testBinary" NOTE: please remove quotes from names above. Burn the CD/DVD and read it using Windows operating system. The folder and file names above must remain intact. Suggestion: remove the "Increase compatibility with Windows System" option in Brasero burn dialog. Brasero just writes the file name into the DVD without transforming its length or casing. The way other CD burning softwares do.
I can confirm that this issue still persists with Brasero 2.28.2. In this case there is no option in the Burn dialog as described above, however the GUI prompts you when you add folders/files >64 chars long that if you don't truncate to 64 chars, the session will be incompatible with Windows. If you chose not to truncate, Brasero burns the data with the full path accessible when mounted under Linux, however when mounting the disc under Windows the heinous truncation described above is evident. Reading wikipedia's Joliet extension article (http://en.wikipedia.org/wiki/Joliet_(file_system)) I can see where the 64 char limit comes from, however I have burnt discs under Nero/Windows XP for years without these truncation issues. Please could you add a setting in Brasero to allow for a flexible path limit? Or if it really is as clear-cut as 103, a setting to permit paths up to and including 103 chars? uname -a: Linux 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 i686 GNU/Linux GNOME version: 1:2.22.2~4ubuntu8 Brasero version: 2.28.2-0ubuntu1
*** Bug 546592 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/58.