Talk:Joliet (file system)

message: Should merge with ISO 9660 — Claunia 22:56, 25 August 2005 (UTC)
thread_title: Merge

message: Does somebody know if FAT-Joliet patents applies also for ISO 9660-Joliet?  faragon 0:52, 12 April 2009 (UTC+2)
:Seems that it is covered US Patent 5758352 - Common name space for long and short filenames, so some trick has to be done in order to avoid the patent.  1:03, 12 April 2009 (UTC+2)  —Preceding unsigned comment added by Faragon (talk • contribs)  
:That patent doesn't cover Joliet in general, as Joliet doesn't specify anything except what is done inside the context of the supplementary volume descriptor, as far as I can see. But if you create a Joliet CD, it has to have a Primary Volkume Descriptor, which means that the long file names in the Joliet section need to be transformed into shorter file name, and in a way that doesn't cause name collisions. The patent cited covers one (or more) methods for doing that.Athulin (talk) 07:27, 25 May 2010 (UTC)
thread_title:  Are there patents covering the the Joliet ISO 9660 Extension? 

message: Joliet (ISO 9660 Extension) redirects to Joliet (file system) - I'm going to swap these around, as (file system) is inaccurate, afaik: Joliet is not a self-contained file system. '(ISO 9660 Extension)' seems a good extension to settle on (see :Category:ISO_9660_extensions). I'm just announcing ahead of time incase there are objections. -- Jon Dowland 14:03, 11 March 2006 (UTC)
replies: text: I think it is better to merge, but, it is a step.—Claunia 14:58, 11 March 2006 (UTC)
thread_title:  (file system) vs. (ISO 9660 Extension) 

message: I don't think it's accurate to say "Most disc-creation software creates both Joliet and Rock Ridge extensions on the disc".  Common Microsoft Windows based disc-creation software just creates standard ISO9660 and Joliet.
:Agreed (neither Nero nor EZ CD Creator, both for Windows, nor Toast nor Apple's CD creation API, both for Mac OS, do this). I'll change that. -- Tempel 07:21, 12 October 2006 (UTC)
thread_title:  Most disc creation software creates... 

message: The origin of the name should really be covered by the article.  The article is not complete without this explanation.  If the above statement can be sourced, please add it to the article.  --Wykypydya (talk) 05:44, 7 July 2011 (UTC)
thread_title: Article needs name information

message: I have updated this section, as I did a deep-dive into Joliet (as contained in http://www-plateau.cs.berkeley.edu/people/chaffee/jolspec.html or http://www.buildorbuy.net/pdf/joliet.pdf) and ISO 9660:1988.
Here's what I found:
* Joliet does not extend ISO 9660 to cover wide characters. 
ISO 9660 is clear that supplementary volume descriptors may contain character set specifications through ISO-2022 mechanisms, as registered by the ISO in International Register of Coded Character Sets (http://www.itscj.ipsj.or.jp/ISO-IR/). And as this registry covers UCS-2 (which is what Joliet uses) as well as UCS-4 character sets, and also UTF-8 and UTF-16, ISO 9660 actually allows wider character sets than Joliet does.
Joliet does make it clear how the chosen character set (UCS-2) should be recorded (most significant byte first). I think ISO 10646 says this already, but it's useful to have it stated directly.
* Joliet changes the rules for directory name construction (ISO 9660 section 9.1.11: Joliet allows '.' to be used in directory names.)
* Joliet changes the rules for how the order of entries in path tables and directories is decided.  In ISO 9660, field of unequal length are padded with space (with file version number, the character '0' is used) to make the entries equally long before they ar compared byte by byte.  Joliet specifies that the pad character should be (00). This affects file and directory names that have trailing spaces, and, if Joliet permits file version numbers (which it is not clear if it does), it also affects the order of entries such as 'AAA.BBB;1' and 'AAA.BBB;10', which in ISO 9660 is unspecified (as appending a '0' to the shorter makes them equal).
* Joliet does extend ISO 9660 as regards file/directory name length (31 -> 128) and directory hierarchy depth (8 to no stated limit -- but can be at most 120).
* Joliet adds a restriction to ISO 9660 in terms of maximum permitted file path length (from 255 to 240). 
* Joliet adds a restriction to ISO 9660 to entirely exclude the characters '*/:;?\' from permitted characters. 
I suspect the idea must have been to exclude those characters from the characters permitted in file names (i.e. the d1 character set in ISO 9660), but the way it is expressed it seems to limit the full a1 character set as well. And as ';' = SEPARATOR 2, required in 9.1.11, this affects the interpretation of file name versions in a way that is not clear. And also, as Joliet has not defined the a1 and d1 character sets appropriately, there is a general unclarity in this area.
It should be noted that I'm still a bit unsure about the length extensions: Joliet is clear that it measures length in bytes, but ISO 9660 is not quite as clear if it is bytes or characters. 
Thus, I don't think it is correct to say that Joliet is an extension of ISO-9660. It extends it in some areas, and restricts it in others.  
Athulin (talk) 08:37, 4 May 2010 (UTC)
replies: text: It is not uncommon to talk of any follow-on specification which modifies an earlier standard as "extending" it, even if there are some tighter restrictions.  I don't see any value in debating the semantics of "extension" here.  :-)  If it bothers anyone, I'd suggest changing the article to use words like "modification", "change", etc.  —DragonHawk (talk|hist) 17:16, 29 May 2012 (UTC)
thread_title:  Joliet: extension or not?