[PATCH 0 of 9 RFC] manage filename normalization policy per repository
mpm at selenic.com
Thu May 31 11:24:23 CDT 2012
On Thu, 2012-05-31 at 23:23 +0900, FUJIWARA Katsunori wrote:
> At Tue, 29 May 2012 15:07:58 -0500,
> Matt Mackall wrote:
> > On Sun, 2012-05-27 at 23:36 +0900, FUJIWARA Katsunori wrote:
> > > Then, what about the another extension plan below ?
> > >
> > > - configures filename normalization policy per root by ".hgeol" like
> > > file
> > Not excited about it.
> > > - warn(or abort) for adding files of which names are normalized in
> > > unexpected style
> > Perhaps. There's not a whole lot a Mac user can do on their end though.
> > > in addition to it, warn(or abort) for adding files colliding with
> > > each other in any normalizations, like case-folding handling
> > Can't happen on Mac. Can happen on Windows and Linux, I suppose.
> > But is it really worth the trouble to fix it? The number of bugs filed
> > related to canonicalization is zero.
> In Japan, people seems to wait for DVCS tools to fix this, because
> they know that this kind of fixing requires long time.
> For example, NFC/NFD handling of SVN was fixed at the end of 2008 at
> last: it was not fixed in main stream but only in the macport version,
Notably we have fixed the bug described at the top of this bug report as
it manifested on Mercurial.
Which means they'll be able to use repositories created by Linux users
just fine, so long as they don't add any files. If they add files, Linux
users will have to fix them (and any references) if they care. That's
not great, but it works.
(Turns out Linux has a display issue with Japanese NFD strings similar
to Windows... even in Firefox!)
Windows will get mojibake in any case due to having a nearly-unusable
UTF-8 situation. And a Mac user certainly won't be able to understand a
repo using Shift-JIS.
So.. can we focus on Windows UTF-8 support first?
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel