[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] sketch of i18n specification
From: |
graydon hoare |
Subject: |
Re: [Monotone-devel] sketch of i18n specification |
Date: |
20 Nov 2003 09:54:17 -0500 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Ori Berger <address@hidden> writes:
> graydon hoare wrote:
> > 1. filenames:
> .. snipped
> > - a filename is a sequence of nonempty path components, separated
> > by byte 0x2F (ASCII / ), and without a leading or trailing 0x2F
>
> And I forgot to add earlier: No path component should be "." or
> "..".
Yes, I had this in an earlier draft; somehow it got ommitted from this.
thanks.
> On Windows, situation's much worse -- you can't have any device name
> as a file name (e.g., "nul", the windows equivalent to "/dev/null",
> virtually exists in every directory on every device) --
>
> but that can't be solved by placing structural limits on file names.
hm. this is a curious situation! can you give more details about funny
things in windows filesystems? I recently found out that windows 95
doesn't actually have very good UCS2 support, and needs a special
library called unicows (see libunicows.sf.net) to function
properly. I'm worried I don't have enough varieties of windows here to
do a decent job testing, nor enough background knowledge of it to make
the right choices.
-graydon