[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Standardizing on UTF8 internally isn't enough

From: Giovanni Bajo <rasky_at_develer.com>
Date: 2007-07-18 09:32:50 CEST

On 17/07/2007 22.55, steveking wrote:

> I don't think that ICU would solve all problems here. Because the
> problem is clearly OS dependent. For example, "NTFS does no Unicode
> normalization at all" (1), so it is possible to have two files with the
> same name (but different composing). If you would enforce either
> composed or decomposed, you'd have simply shifted the problems from the
> Mac to Windows.

While this is tecnically true, I dare you finding a program that lets an user
create a filename in NFD form on Windows. On other hand, *right now*, Mac (or
better: HFS+) is totally broken with Subversion, because *any* filename
subjected to different NFC/NFD form is broken.

There is no silver bullet here. Both Linux and Windows allow to create two
files (in the same directory) whose names which normalize to the same name.
This is unsupported by HFS+. So you can't really "win".

But you can solve *most* problems by normalizing. As I said, I think that once
the Mac problems are solved, you're *very* unlikely to get a bugreport from a
Windows user.

Giovanni Bajo
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 18 09:32:16 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.