#2 Unicode Error on Startup on Japanese WinXP

[shock_ez]

Starting Metamorphose in a native-Japanese (not just
Japanese enabled) XP environment yields a unicode error.

"UnicodeEncodeError: 'cp932' codec can't encode
character u'\xe9' in position 1: illegal multibyte
sequence"

Please see the attached logfile.

Tested on v0.2.3a and v0.2.2, both exhibit the error.

NOTE: v0.1.6 does NOT exhibit the error.

[shock_ez]

Metamorphose Log

[ianaré]

Logged In: YES
user_id=1331150

Thank you for your help.

in version 1.6 I had: "M\xe9tamorphose"
in version 2.3a I had: u"M\u00e9tamorphose"

I did that to fix a different encoding error. Arg!

I am working on a version which uses all unicode characters
and should theoretically work with any character set. I'll
compile the latest build and post it here as an attachement.

If you would test it for me I would appreciate it. I tested
displaying and entering in japanase characters, but I do not
have access to a japanese version of XP.

[ianaré]

Logged In: YES
user_id=1331150

I got a server error uploading the file. Go to:

http://file-folder-ren.sourceforge.net/dev_src/

and dowloand the setup.exe file, the others are sources.

[shock_ez]

Logged In: YES
user_id=1314529

Version 0.3.0 installs and runs successfully. Excellent.

When you mentioned your naming schema I did have a thought.
I looked back, remembering that the way the "Metamorphose"
name displays in Japanese XP is weird. I've seen this
behavior before in other programs whose unicode is something
that the OS "doesn't like" (I wish I had a technical
explanation). Take a look at the screenshot of my start
menu. It must be the accent mark that is causing such
behavior, and even possibly what caused the error before.

[shock_ez]

Wonky display screenshot

[ianaré]

Logged In: YES
user_id=1331150

I'm glad the new version works.

As for the start menu that is from the installer, forgot
about that... I think i'll just take out the accent there,
unless I can figure out how to add unicode characters to the
installer. So for the next official release it should be all
good.

If i'm not mistaken windows defaults to some windows-only
character set, based on the language. What happens is a
character encoded in my language setting becomes another
character in yours. Only if we are both using the same
encoding will the character show properly.
This is why i moved to unicode, as it theoretically displays
all characters from all languages... Giving the posibilty of
mixing japanese, hebrew and greek texts in the same
application for example.

Thanks again.