Branko Čibej wrote on Tue, Feb 22, 2011 at 19:41:12 +0100:
> On 22.02.2011 18:17, Julian Foad wrote:
> > For example, a solution that involves normalizing all input to NFD would
> > have the advantages that on MacOSX it would need to do *no* conversions
> > and would continue to work with old repositories in Mac-only workshops.
> You'd make this configurable? But how? How do you prove that paths in
> old repositories are normalized in a certain way? You can only assume
> that for paths that you know were normalized before being written to the
> repository. And even then, you can't assume too much -- an older tool,
> without normalization, can still write denormalized strings to the
> repositury vial file://. Unless you want to have an explicit flag for
Really? So the FS layer wouldn't be aware of NFC v. NFD?
Right now the FS layer already requires paths to be in UTF-8; we might
as well declare that the FS layer considers two paths equivalent if they
only differ in canonicalization, and then have the FS canonicalize paths
before storing them.
> every path to see if it's normalized or not -- which implies changing
> the repository format -- then you can only really make assumptions about
> normalization of paths in the repository post-2.0.
> -- Brane
Received on 2011-02-22 20:17:00 CET