Closed GoogleCodeExporter closed 9 years ago
We've recently fought with file system and console encodings (issue 454, issue
446,
issue 509), and although the battle was hard we survived. With the knowledge we
gained fixing this issue ought to be relatively easy too.
Original comment by pekka.klarck
on 29 Mar 2010 at 10:34
Took a fast look at this and it really seems we can implement this pretty
easily. I
actually already committed a fix in r2792 but I still need to look at this with
Janne
(my comrade in the Unicode wars), test on Windows, and try to add a
platform/interpreter agnostic acceptance test.
Original comment by pekka.klarck
on 29 Mar 2010 at 10:55
The original implementation didn't work when there were characters that the
console
couldn't show. That ought to be fixed in r2828. Tests are still missing...
Original comment by pekka.klarck
on 31 Mar 2010 at 4:22
Added tests in r2885. This still needs to be tested on Windows and I want to go
through the code with Janne.
Original comment by pekka.klarck
on 8 Apr 2010 at 9:02
Implementation gone through and slightly modified with Janne. Tested on Windows
both
with Python 2.6 and Jython 2.5. Needed to update tests because the Windows
console
supports a pretty limited set of characters and some of the chars shown
correctly on
Ubuntu with UTF-8 aware console were shown as '?'. We simply cannot show chars
the
console doesn't support so this is as done as it can be.
Original comment by pekka.klarck
on 12 Apr 2010 at 3:27
This issue is included in RF 2.5 alpha 1.
Original comment by jussi.ao...@gmail.com
on 6 May 2010 at 1:35
Original issue reported on code.google.com by
Andreas.EbbertKarroum@gmail.com
on 29 Mar 2010 at 10:23