[PATCH stable v2] convert: use original local encoding when converting from Perforce

Matt Mackall mpm at selenic.com
Wed Jul 22 14:13:11 CDT 2015

On Wed, 2015-07-22 at 18:49 +0100, Eugene Baranov wrote:
> In my environment p4 seems to use default system locale (windows-1252)

It generates 1252-encoded bytes on the command line? Is your command
line environment in cp437 or similar? This is Mercurial's strategy on
Windows (ignore the OEM code page, only pay attention to the ANSI code
page) so I like it, but optimally we'd use UTF-8 for transferring
metadata across and a configurable encoding for filenames.

> for the output which results in some fancy character like "smart
> quotes" (“ 201C and ” 201D) to be lost if Latin1 is used.

When you say 'lost', do you mean they replaced with '?' or mojibaked?

Mathematics is the supreme nostalgia of our time.

More information about the Mercurial-devel mailing list