On 31/01/2009 4:16 PM, Mark Tolonen wrote:
"Mark Hammond" <skippy.hamm...@gmail.com> wrote in message
news:4983818b.1090...@gmail.com...
Please file a bug and I'll try and nail it before the next release
(pythonwin itself is now much more unicode aware - it now even allows
each file to have its own encoding - but I'm yet to implement the
encoding detection beyond detecting a BOM...)
Note I'm not that familiar with changing language etc options, so
please try and be as explicit as possible in the repro steps.
No problem. I'll do it tonight. I'm looking forward to your release.
IDLE handles Chinese, but I like the PythonWin interface better.
While the recent pythonwin unicode changes are in my head, I've had
another play. I upgraded Scintilla and implemented the suggestion from
Elias, implemented pep283 support (yay!) and have managed to get things
working correctly everywhere I've tested (editing, printing
interactively, running, copy-pasting, etc) with the appropriate unicode
character being displayed and/or saved in the correct encoding. My
testing is done with "simple" extended characters (eg, the "copyright
symbol, \xa9, or "hold alt down while pressing 0169 on the numeric
keypad" :) so I may yet be missing some more complex cases.
If either of you - or anyone else with experience in this area - are
brave and willing to test this out, I'll send you an email with the
location of a build you can grab and see if (or hopefully how <wink>)
things have improved.
Thanks,
Mark
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
