The semicolon does not have a special meaning on Unix file systems. (It does, however, have a special meaning in typical Unix command-interpreters ["shells"], which is insignificant for this specification).
Delete list item.
Line 26f Part 2, section 9.2.5
ed
Proposed Disposition of DIS 29500 Comment DE-0156 (Modified: 2007-12-07) Agreed; the following change will be made to Part 2, ยง9.2.5, page 33, line 26: [Example: Examples of these limitations are: On Windows file systems, the asterisk (”*”) and colon (”:”) are not valid, so parts named with this character will not unzip successfully. On Windows file systems, many programs can handle only file names that are less than 256 characters including the full path; parts with longer names might not behave properly once unzipped. On Unix file systems, the semicolon (”;”) has a special meaning, so parts with this character might not be processed as expected. end example]
