This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#8174 - path length of >= 256 bytes is problematic?
Attached to Project:
Rockbox
Opened by robert jacobs (rnjacobs) - Saturday, 17 November 2007, 07:25 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Tuesday, 24 June 2008, 12:45 GMT+2
Opened by robert jacobs (rnjacobs) - Saturday, 17 November 2007, 07:25 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Tuesday, 24 June 2008, 12:45 GMT+2
|
Details(This is on a Nano 1st Gen)
I have a specific filename that rockbox cannot open. The same file, in any other directory, or with any other name, is openable; any arbitrary file with this name cannot be played or "Properties"ed. The path that fails is "Brahms/CUdL+MITCC-Ein_Deutches_Requiem/(Chœur_Universitaire_de_Lausanne,_MIT_Concert_Choir,_Sinfonietta_de_Lausanne,_Jean-Christophe_Aubert_directing-Johannes_Brahms's_Ein_Deutsches_Requiem)-2-_Denn_alles_Fleisch,_es_ist_wie_Gras_[2006_May_31_&_June_1].ogg" Rockbox can display the file in the browser (the œ is displayed as the "no glyph" character, whatever). I discovered this is not a unicode thing (All the other files in the same dir have the same œ; plus the same non-functioning file works if e.g. copied to the root directory) This seems to be a maximum length thing. Neither this file nor the one that is 5 characters longer (256 and 261 unicode entities long) can be played. This may be related to the maximum of 255 ucs2 entities for a filename (not path!) on VFAT. (I probably should use shorter filenames, but...) Thank you very much for an awesome piece of software! |
This task depends upon
Closed by Jonathan Gordon (jdgordon)
Tuesday, 24 June 2008, 12:45 GMT+2
Reason for closing: Not a Bug
Additional comments about closing: use shorter filenames...
Tuesday, 24 June 2008, 12:45 GMT+2
Reason for closing: Not a Bug
Additional comments about closing: use shorter filenames...
(Looking up the standard, microsoft seems to say "260 bytes, including the [driveletter]:\[nul]", which is a max of 256, not 255, but that's just being pedantic)