Add code to 'fix' python encoding and it's unit test.

Add code to 'fix' python encoding and it's unit test.

With this code in action, I can successfully print arabic and chinese on linux
and cygwin. It fails to print chinese on my Mac but prints arabic. It prints '?'
on Windows console but it *doesn't throw* which is the biggest improvement here.
It was particularly a problem on windows because WindowsError's description text
is in the current ANSI code page so it failed to print if the text was not pure
ASCII, like error message when using Windows' French UI.

R=dpranke@chromium.org
BUG=none
TEST=manual unit test ./tests/fix_encoding_test.py and it shouldn't throw

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=79006

[Dirk Pranke, 2011-03-22 18:22:22]

LGTM with one possible change ... should we add this to git-cl as well?

Ugh. What were you doing that caused you to have to do this? Was it running in
the French locale?

[M-A Ruel, 2011-03-22 18:24:23]

On 2011/03/22 18:22:22, dpranke wrote:
> LGTM with one possible change ... should we add this to git-cl as well?

Can you move git-cl up a directory first? :)

> Ugh. What were you doing that caused you to have to do this? Was it running in
> the French locale?

Yep. But even just printing unicode in bash when the default encoding is set to
'ascii' would blow up on mac and linux so it's not only a windows-specific
issue.

M-A

[Dirk Pranke, 2011-03-22 18:31:10]

Okay.

On Tue, Mar 22, 2011 at 11:24 AM,  <maruel@chromium.org> wrote:
> On 2011/03/22 18:22:22, dpranke wrote:
>>
>> LGTM with one possible change ... should we add this to git-cl as well?
>
> Can you move git-cl up a directory first? :)
>
>> Ugh. What were you doing that caused you to have to do this? Was it
>> running in
>> the French locale?
>
> Yep. But even just printing unicode in bash when the default encoding is set
> to
> 'ascii' would blow up on mac and linux so it's not only a windows-specific
> issue.
>
> M-A
>
> http://codereview.chromium.org/6676090/
>