On Sep 24, 2005, at 2:18 AM, Adib Taraben wrote:
NSIS is already translated into several languages including Hebrew, Chinese, Korean, Japanese. But For your own strings you have to add your translations. We need translators for those strings to have also Japanese etc. I dont know how this Unicode thing should work. But remember it should still work under Win98 where Unicode is not implemented. What exactly do you have in mind?
I've in mind to get it using Unicode internally, but then convert to local ANSI when going to the API's. Among other things, that's the way that MS Office and their other products work, so that they can ship a single binary for both Win9x and WinNT/2k/XP. I'm working with NSIS people to make sure I can help them do this in a way that works with their goals.
There's some info on this on the Wiki I put up a while back
http://wiki.inkscape.org/cgi-bin/wiki.pl?Win32Port
Oh, and one of the issues this would fix is for any non-English Windows XP users. For example, if your local user directory path contains non-Latin-1 or the "all users" home directory does, installation will fail if your current ANSI code page is set to anything that does not include those.
What exaclty is it what you want to peek/poke? The inkscape runtime language is detected by the gtk not NSIS. For now we have far less NSIS translations than inkscape languages. I would be happy if this "select language from menue" feature works because this language selection is very tricky. There is only one issue that I can see: [ 1246690 ] Interface is right-to-left 0.42 on XP with Hebrew support
There's a common thing where the Windows box is set to one language/ locale, but the user's current default is a different language.
Inkscape currently counts on glib for this, which in turn counts on the Unix-style LANG environment variable. This is good for Linux people on a Windows box, but fails for the average Windows user.
So basically Inkscape on Windows is ignoring Windows-style language API's and instead only goes by Unix-style environment variables. This is correctable, and would improve the user experience on Windows greatly.