Fwd: [Bug 340394] Re: redirecting log output to a file produces the wrong encoding on win32

[Martin Pool]

https://launchpad.net/bugs/340394

Does anyone have a clear idea of
1- what output encoding bzr should use on Windows when output is
redirected to a file and running in a terminal using cp850?
2- what mechanism if any should be available to control it?

I suppose we could (like svn?) have a parameter that specifies the
output encoding...

-- 
Martin




---------- Forwarded message ----------
From: Wouter van Heyst <larstiq+launchpad at larstiq.dyndns.org>
Date: 2009/4/19
Subject: Re: [Bug 340394] Re: redirecting log output to a file
produces the	wrong encoding on win32
To: mbp at sourcefrog.net


On Thu, Apr 09, 2009 at 01:39:12AM -0000, Martin Pool wrote:
> Thanks Tim.
>
> It looks like that's in IBM-850 (aka cp850), with ü as codepoint 0x81
> and ö as cp 0x94.  It may be that cp850 is the right thing to write to
> the terminal but if you're in a utf-8 locale and redirected to a file it
> should probably write utf-8.

Drive-by-bug-commenting: aren't the filesystem encoding and the terminal
encoding seperated in Windows? I recall bialix having trouble in that
area in the past.

Wouter van Heyst

--
redirecting log output to a file produces cp850 on win32
https://bugs.launchpad.net/bugs/340394
You received this bug notification because you are a member of bzr-core,
which is the registrant for Bazaar.

Status in Bazaar Version Control System: Confirmed

Bug description:
"bzr log > log.out" on win32 where the commit messages contain
non-ascii characters seems to produce invalidly encoded output.  It
works correctly on Linux, and it produces the correct output in a
cmd.exe window.

----------------

When saving the log output to a file, this should be saved in UTF-8
encoded form.

Please also refer to:
https://answers.edge.launchpad.net/bzr/+question/63601





-- 
Martin <http://launchpad.net/~mbp/>