On Nov 30, 2007 10:58 PM, Tex Texin <[EMAIL PROTECTED]> wrote:
> Bjoern,
>
> If we are discussing reasonable, reasonable software does not use CP437 as an 
> encoding, for at least the last 10 years. ;-)
>
> FWIW, a reasonable software system wouldn't allow drawing characters in a 
> name, but DOS did, and so many users did use smiley faces, card suits, and 
> the like in their file names. Generated filenames often used them.
>
> If we were talking about ancient zip files, then we might have to tolerate 
> such names. But as we are discussing new specs, instead of supporting all 
> possible zip files, why not specify the use of zip files, with the constraint 
> that filenames be stored as utf-8, and make the non-utf-8 names unacceptable. 
> Perhaps with modern tools, this isn't a problem.

One of our design principles [1] for the Widget spec is that authors
should be able to create widgets just using the zipping tools that
have been pre-packaged with an OS. Because the introduction of
allowing UTF-8 names in Zip is a very recent addition to that spec, we
might not see implementations for a long time.

> I would like to preserve the ability of authors to use non-ASCII file and 
> pathnames.
> We can still suggest that non-ASCII characters may cause problems.

Done.

> Separately, but related, a problem with filenames is case-sensitivity. It is 
> not uncommon to have problems installing a zip file, authored on a 
> case-sensitive system, onto a case-insensitive file system, due to collisions 
> and possible overwrites being detected.
> It might be good to warn authors to avoid this problem as well.

The widget spec currently mandates that a widget engine treat file and
folder names as case insensitive. I have still to spec how to deal
with filename collisions (ie. halt, ignore, or override? However, that
probably a subject of a different thread. If anyone has any comments
regarding that, please send them to the WAF list:)).

Kind regards,
Marcos
[1] http://dev.w3.org/2006/waf/widgets-reqs/
-- 
Marcos Caceres
http://datadriven.com.au

Reply via email to