problems with mod extraction in windows?

[titi]

Hagekura and someone else had problems installing the japanese tech tree from the mod section.
Downloading was fine, but it looks like the extraction failed. See here:
https://forum.megaglest.org/index.php?topic=6103.msg72961#msg72961

Is there a problem in windows extracting mods automatically?
Can anyone establish that it works/works not  in windows?

[ultifd]

Fine for me, Windows 7 32-bit.

[Hagekura]

For reference, The japanese guy who also has same problem on direct downloading uses Windows XP(32bit). I'm also using XP 32bit.

[softcoder]

Can you confirm that the path to your appdata folder in windows does not contain non ascii characters? (the folder where mods are stored by default in windows)?

[Hagekura]

Can you confirm that the path to your appdata folder in windows does not contain non ascii characters? (the folder where mods are stored by default in windows)?

Hi, In the XP megaglest's default user data path is under C:\Documents and Settings\ .

The japanese guy confirmed that Direct Download works when he create C:\test\megaglest\ and copy all the data files of $APPDATA\megaglest\ to the test folder, then edit the line in glest.ini "UserData_Root=C:\test\megaglest\" on trial. then it worked.

[tomreyn]

So the problem does indeed seem to be that the Windows username contains non ISO-8859-1/LATIN-9/"ASCII" characters (which seems to be legitimate in terms of Windows, which seems to be able to handle this) and thus in the path to the users' Documents and Settings directory (which, on XP, defaults to %AppData%\megaglest and thus to, e.g. C:\Documents and Settings\USERNAME\Application Data\megaglest), but MegaGlest is unable to handle such characters and still relies on this location to be accessible by default.

[Omega]

What change would MegaGlest have to do to have full character support? I'd assume UTF-8? Would also be very good for translations, which are hindered by the fact that non ASCII characters cannot be used.

[softcoder]

This this appears to be a bug on windows platform only and is related to the windows API that retrives the users appdata folder (as we all know glest / megaglest do not yet support widestrings nor utf). I have enabled the Japanese character set and am testing to see if there is a simple way to support file paths with special language characters (this does not mean full text support for these special characters). All of this works in Linux with the current 3.5.x mg code (I tested with Japanese characters in the mod foldername and everything was perfect (however it did not work in XP).

*UPDATE: Ok i have a windows binary located on my webasite for people with non ascii file paths (like Japan). Please give this a try and let me know if it works?

www.soft-haus.com/glest/temp/megaglest3.5.1_i386_win32_bin.7z

I enabled unicode and added some handling of wide characters and tested on my Windows XP machine by enabling Japan locale and character set. I also create a Japanese user and ran successfull as this being my mod path:

Code: [Select]

C:\Documents and Settings\人間五\Application Data\megaglest
Thanks