> On 02.02.2012 20:22, Peter Samuelson wrote: > > By proposing a client-only solution, I hope to avoid _all_ those > > questions.
[Branko Cibej] > Can't see how that works, unless you either make the client-side > solution optional, create a mapping table, or make name lookup on the > server agnostic to character representation. Yes, I did propose a mapping table in wc.db. Old clients on OS X would continue to be confused; the solution is to upgrade. New clients on OS X (and elsewhere) would maintain a mapping table between 'repository path' and 'local filesystem representation'. We already have these two concepts, given we support non-UTF-8 client encodings. > It would be nice if we could normalize paths in the repository > without having to perform a dump/reload cycle, but I don't know how > that would work in FSFS Indeed, it's a problem similar to obliterate, and carries the same risk of invalidating every wc. This is why I don't think it's a reasonable path to take in the short term (1.x). Peter
