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 323506 - warm when filename truncated
warm when filename truncated
Status: RESOLVED OBSOLETE
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
2.14.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
: 421735 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-12-07 22:39 UTC by Francois Poulain
Modified: 2009-07-29 10:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
Patch (2.06 KB, patch)
2008-12-18 20:42 UTC, Fabio Bonelli
none Details | Review

Description Francois Poulain 2005-12-07 22:39:39 UTC
Version details: 2.12.1
Distribution/Version: gentoo

From:  <fpoulain@enib.fr>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.12.1
Subject: Feature request on nautilus-cd-burner

Distribution: Gentoo Base System version 1.6.13
Package: nautilus-cd-burner
Severity: enhancement
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Gentoo
Synopsis: Feature request on nautilus-cd-burner
Bugzilla-Product: nautilus-cd-burner
Bugzilla-Component: cd-burner
Bugzilla-Version: unspecified
Description:
Please describe your feature request:

I have burned a CD for a friend, and I had a file with a very long name,
it were hashed without I was said. Can you put a warning message, or a
renaming window ?

Thank you for all ...
Comment 1 Baptiste Mille-Mathias 2006-01-25 19:54:10 UTC
I think this is not an enhancement but a bug, so I change the severity to major, because it change the data stored on the disk.
Comment 2 Fabio Bonelli 2006-05-21 20:52:23 UTC
We need a GUI to present the eventual file renaming, when files with certain names can't be, for whatever reason, written to a disc (see also bug 341622). 

What about this one:
__________________________________________________________
|                                                         |
| [Warning icon] Invalid filenames, blah blah blah        |
                 ,-------------------------------------.  |
                 | Old name        |    New name       |  |
                 |-------------------------------------|  |
                 |Hello/Foobar.mp3 |  Hello_Foobar.mp3 |  |
                 |More:invalid.avi |  More_invalid.avi |  |
                                                          |
                 |     [...]                           |  |
                 |                                     |  |
                 `-------------------------------------'  |
                                                          |
                                  [Cancel]  [Proceed]     |
__________________________________________________________|

The new name column would be filled with proposed filenames, but editable.
Any suggestions?
Comment 3 Fabio Bonelli 2006-10-06 07:56:33 UTC
*** Bug 359997 has been marked as a duplicate of this bug. ***
Comment 4 SchAmane 2006-10-06 08:20:24 UTC
Somebody marked my bug as duplicate. I will mention that my report is not a duplicate of this bug. Its hasnt nothing to do with very long names in mkisofs. That bug i have also.
But what i was reported happends only for DVD burning on the fly. Under windows every file name (also short names) are complete mess.
Please reopen my bug as standalone and read report again.
Comment 5 Fabio Bonelli 2007-03-23 17:26:17 UTC
*** Bug 421735 has been marked as a duplicate of this bug. ***
Comment 6 Fabio Bonelli 2008-12-18 20:42:31 UTC
Created attachment 124965 [details] [review]
Patch

The patch pops up the rename dialog with long file names renamed to shorter ones.

I limited them to 64 UTF8 characters, the Joliet limit, since we use Joliet by default.
Comment 7 Bastien Nocera 2009-07-29 10:47:27 UTC
nautilus-cd-burner has been replaced by Brasero in the GNOME 2.26 release. If your bug still applies to Brasero, please feel free to re-open the bug, and reassign it to brasero itself.