Unicode Windows API, Was: Concerns about using Python's ctypes library on Windows

[박경국]

Ok, I am relieved as I found out there are others.

As I wrote in my previous e-mail, the reason I had to
use fixutf8 was because my repo was converted from subversion.
As a subversion repo stores everything in UTF-8 even on Windows
and 'hg convert' does not support transcoding, there is no way
to make a conversion correctly.

I had once submitted a small code to this mailing list
hoping a kind developer fix this but it didn't attract anyone's interest.
As a mercurial user living on multi-byte Windows, sometimes I feel lonely.

http://mercurial.808500.n3.nabble.com/issue2223-File-name-encoding-issue-in-hg-convert-td866606.html

Kyung-Kook




On Mon, Aug 1, 2011 at 16:45, Adrian Buehlmann <adrian at cadifra.com> wrote:
> On 2011-08-01 03:57, 박경국 wrote:
>>> We are certainly not going to rewrite TortoiseHg to spawn a process per
>>> repo just to support someone's weird setup who wants to use something
>>> like fixutf8 in repo A but not in repo B and open both in the same
>>> TortoiseHg window. If a function is wrapped by an extension, it is wrapped.
>>
>> I can't understand why you are calling my case a weird setup.
>
> Maybe the weirdness is more in how fixutf8 tries to solve your problem.
>
> Perhaps you should talk to its creator or those who maintain it currently.
>
>> Is there any other way for me to avoid it without abandoning using TortoiseHg?
>
> Currently: Not that I know of, without rewriting TortoiseHg.
>
> TortoiseHg uses a single process that loads python and extensions. thg
> links with the mercurial sources and if an extension wraps a function of
> the mercurial python modules, that function is wrapped for TortoiseHg
> globally. Assuming that this wrapping is limited to a specific repo
> apparently doesn't work.
>
> And I've explained that you probably have the same problem with subrepos
> that use fixutf8 too (no need to invoke the "TortoiseHg should be
> rewritten card").
>
> But someone might be able to add a single-repo-lockdown-mode feature for
> TortoiseHg 2.X. Just watch out for some potential surprises in thg's
> repo registry.
>
>