Closed GoogleCodeExporter closed 8 years ago
This is due to the fix for issue 94. It "only" affects the custom codepages
actually, in particular the ISO ones, which of course are used by default.
UTF-8 and
the Windows codepages are fine though. Hence, as a workaround, the codepage on
the
Fonts panel of the options can be set to one of the Windows codepages, e.g.
1252
for "Western" users.
Apologies for letting this shamefully obvious bug slip through.
Original comment by andy.koppe
on 28 Apr 2009 at 3:03
Thank you very much for the workaround. When I set the codepage as you
suggested, my
title works. What may be shamefully obvious to you is obscure to me. I didn't
even
know to check the codepage setting.
Original comment by barry.do...@gmail.com
on 28 Apr 2009 at 3:54
Fixed in r269 on 0.3 branch and r270 on trunk, by extending mb_to_wc do deal
with
custom codepages.
Original comment by andy.koppe
on 28 Apr 2009 at 8:23
Original comment by andy.koppe
on 29 Apr 2009 at 8:43
Original issue reported on code.google.com by
barry.do...@gmail.com
on 28 Apr 2009 at 2:49