[PATCH 0 of 9 RFC] manage filename normalization policy per repository
Matt Mackall
mpm at selenic.com
Sun Jun 3 17:52:30 CDT 2012
On Sat, 2012-06-02 at 23:36 +0900, FUJIWARA Katsunori wrote:
> At Fri, 01 Jun 2012 13:56:17 -0500,
> Matt Mackall wrote:
> >
> > On Fri, 2012-06-01 at 18:20 +0900, FUJIWARA Katsunori wrote:
> > > > So.. can we focus on Windows UTF-8 support first?
> > >
> > > We, some developers in Japan, start for "Windows UTF-8 support" !
> >
> > Ok, in case you didn't see it, I wrote an outline of my idea here:
> >
> > http://mercurial.selenic.com/wiki/WindowsUTF8Plan
>
> Thank you for creating page !
>
> In addition to what you described in WindowsUTF8Plan, I think some
> process interaction parts should be fixed:
>
> - receiving arguments in Unicode:
>
> when all managed filenames are encoded in UTF-8, some characters
> can't be re-encoded into system code page (e.g.: NFD characters on
> cp932 environment).
That's addressed right here, actually:
http://mercurial.selenic.com/wiki/WindowsUTF8Plan#Console_will_still_be_legacy
In short: "we're not thinking about this now".
I think if you try to tackle the filesystem and command line encoding
issues in parallel, you will almost certainly fail to make the reviewer
happy.
> BTW, in transition period, repositories using different encodings for
> filenames may exist in same host: cp932 and utf-8, for example.
Huh? Please go read that page again, because I don't think you
understood it:
http://mercurial.selenic.com/wiki/WindowsUTF8Plan#Definitions
http://mercurial.selenic.com/wiki/WindowsUTF8Plan#Upgrading_to_UTF-8
I fully expect SINGLE repos to have different encodings in different
changesets. This is in fact what will allows us to upgrade them. There
will be no notion of "repository encoding".
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list