RFC: safe pattern matching for problematic encoding

[FUJIWARA Katsunori]

At Wed, 23 May 2012 13:57:27 -0500,
Matt Mackall wrote:
> 
> On Wed, 2012-05-23 at 22:07 +0900, FUJIWARA Katsunori wrote:
> 
> > # in fact, to cooperate MacOS users, NFD for filenames should be
> > # solved, too. I'm experimenting an idea to solve it, and will post it
> > # soon
> 
> I consider this solved already.

Sorry for not enough explanation.

With current implementation:

    1. add the file, of which name is changed by NFD, on MacOS
    2. receive such changeset on other platforms, and then,
    3. NFD-ed file is stored into working dir by "hg update"

Of course, for some people, this is co-operative enough.

But at least in Japan, users on platforms other than MacOS strongly
want to get non NFD-ed files on their working directory.

# both via GUI file browsers and CUI terminals

For example, "i18n/ja.po" message translation file contains 122181 non
ascii Japanese characters and 10% of them can be changed by NFD: this
ratio may become 15% or more in some situation.

This is not less for users using Japanese.

Yes, this requrement is not logical but emotional. And because it is
emotional reason, it is so important to spread Mercurial in Japan :-)


BTW, in Japan, non-programmer people (e.g.: graphic designers and
project managers) seems to want to use MacOS, and they are main users
of filenames in Japanese.

# of course, there are many programmers loving MacOS, too :-)

But in other hands, many of them use Windows, also.

So, people leading introduction of Mercurial into their teams often
ask me how to co-operate with them via Mercurial.

----------------------------------------------------------------------
[FUJIWARA Katsunori]                             foozy at lares.dti.ne.jp