Ph. Marek wrote:
>> 4) Teach the svn_path_local_style()/svn_path_internal_style() pair to do
>> perform reversible mappings of the file name, similar to what Martin
>> proposed about colons; for example, you could map all "weird" characters
>> to some visually equivalent Unicode code point that happens not to
>> confuse the Windows API. That way our internal file names would always
>> be correct, and the local ones would always be acceptable to Windows.
>>
>> I think that actually wouldn't be all that hard to do, assuming we can
>> find a sensible set of mapping rules.
>>
> That seem to be a good solution; but I'm afraid that the definitions are not
> that simple.
>
> If you just replace every . with a similar unicode character, windows won't
> recognize the filetype, and DOS-programs would see abc.txt (with . as unicode
> character) as abc~12345.txt or something similar.
>
> So you'd have to make substitution depending on position in filename (only at
> start at end or everywhere) per character; and it's likely that that won't
> solve all problems ...
>
> Imagine some user creating files with that unicode-characters - then you'd
> possibly overwrite local files without even knowing.
> I know that this may be rare .... but that's the first case of "filename....."
> too.
>
Yep, I'm aware of all that. I didn't mean to imply it would be trivial. :)
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 9 11:20:58 2006