http://bugzilla.wpkg.org/show_bug.cgi?id=5 Rainer Meier <skybeam at users.sourceforge.net> changed: What |Removed |Added Status|RESOLVED |CLOSED --- Comment #3 from Rainer Meier <skybeam at users.sourceforge.net> 2007-11-19 19:02:18 --- No reaction since years. I assume it works. Actually WPKG is currently reading the local language from the registry but it is reading the LCID value (see http://www.microsoft.com/globaldev/reference/lcid-all.mspx) instead of the three-letter acronym. This allows more fine-grained language configuration. As proposed I would prefer launching wpkg.js from a batch file which actually exports the language code of the client before running wpkg.js. If it is enough to hard-code it you might also consider just setting the language code within the <host /> or <profile /> node: <host ...> <variable name='LANG' value='enu' /> </host> <profile ...> <variable name='LANG' value='deu' /> </profile> -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |