Message6325
I can reproduce this issue on OS X, but on this platform, your test case ends up being invalid for a couple reasons:
1) When I compile this under OS X javac the a w/ umlat char is not interpreted correctly -- because the OSX file.encoding defaults to MacRoman. Make sure the file.encoding value for your platform is what you think it is (it should be utf-8 since that's how your .java file is encoded). You can force the encoding by specifying -encoding utf8 to javac
2) When I force javac's encoding to utf8 the generated file.py is correct but the test still fails. That's because it's comparing raw utf-8 encoded bytes (as a Python str) to a Java string. If you instead declare the ae variable as a Python unicode str (change ae = '<ae from java>' to ae = u'<ae from java>' ) the test passes |
|
Date |
User |
Action |
Args |
2011-01-19 01:01:38 | pjenvey | set | messageid: <1295398898.68.0.858753080219.issue1696@psf.upfronthosting.co.za> |
2011-01-19 01:01:38 | pjenvey | set | recipients:
+ pjenvey, jpulakka |
2011-01-19 01:01:38 | pjenvey | link | issue1696 messages |
2011-01-19 01:01:38 | pjenvey | create | |
|