>I found a CD that looks a bit strange. > >Is there anybody who really knows Joliet and can help? > >The SVD of the CD contains escape sequences that I would call buggy: > >The first bytes are: 0: '%' 1: '/' 2: 'E' 3: ' '
Certainly looks like a bad escape sequence - for UCS-2 Level 3 it should be: %\E >and from esc[3] .. esc[31] all characters are spaces instead of nuls. > > Mkisofs uses nuls. As the Joliet spec states that the escape sequences conform to the ISO9660 standard for the Supplementary Volume Descriptor (section 8.5.6), then the remaining bytes should be nulls. >In addition, the Joliet repesentations of the filenames look strange: > >d--------- 0 0 0 2048 Feb 5 2002 [ 420] . >d--------- 0 0 0 8192 Feb 5 2002 [ 344] .. >---------- 0 0 0 4304 Dec 20 2001 [ 159908] ipc.h.html;1 >---------- 0 0 0 136 Dec 12 2001 [ 159907] list.;1 ... > > Mkisofs never adds ';1' to joliet filenames. I had an email exchange with Eric about this when he first added Joliet to mkisofs - the Joliet spec (which is written as if it were an addition to the ISO9660 standard) states that: "Simply put, SEPARATOR 1 and SEPARATOR 2 shall be expanded to 16-bits". SEPARATOR 2 is ';' - which is used signify the version number of a file. So, the Joliet spec allows for file version numbers, but as Eric was implementing Joliet using Joliet CDs he had available - which didn't have version numbers, he decided to leave off the version number. So theoretically, having version numbers follows the Joliet spec, so mkisofs is doing it wrong, but as all (??) Joliet readers seem to ignore whether there are version numbers or not, I don't think this is a problem. However, having an incorrect escape sequence doesn't follow the Joliet spec or the ISO9660 standard. James Pearson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
