On Tue, Jan 19, 2010 at 12:43 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Sat, Jan 16, 2010 at 6:42 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Markus:
The point is that translations should be enabled
also for CMD line usage which requires as far as I understand a change
in Init.bat (?).
On Windows, Init.bat should set LANG (or at least LC_MESSAGES and
LC_CTYPE). But LANG needs to be in Unix format (e.g. "ja_JP"), while
Windows provides a numeric code. So we need some way to get the
appropriate LANG value from the Windows locale setting.
Thanks for r40533 which I have backported to 6.4 (r40540) and 6.5 (r40539).
When launching latest winGRASS-SVN (self compiled) in the MinGW shell,
the LANG and LC_MESSAGES are not set.
Do we need a similar change in Init.sh for MinGW?
When launching latest winGRASS-SVN (self compiled) in the
MinGW shell, the LANG and LC_MESSAGES are not set.
Do we need a similar change in Init.sh for MinGW?
note that mswindows/GRASS-Installer.nsi dynamically creates both
.sh and .bat launchers which may need adjustment.
>>> The point is that translations should be enabled
>>> also for CMD line usage which requires as far as I understand a change
>>> in Init.bat (?).
>>
>> On Windows, Init.bat should set LANG (or at least LC_MESSAGES and
>> LC_CTYPE). But LANG needs to be in Unix format (e.g. "ja_JP"), while
>> Windows provides a numeric code. So we need some way to get the
>> appropriate LANG value from the Windows locale setting.
>
> Thanks for r40533 which I have backported to 6.4 (r40540) and 6.5 (r40539).
When launching latest winGRASS-SVN (self compiled) in the MinGW shell,
the LANG and LC_MESSAGES are not set.
Do we need a similar change in Init.sh for MinGW?
Hmm; MSys[1] users should be setting LANG (etc) in ~/.bash_profile
(etc) if they want it set.
[1] MinGW is gcc + binutils; MSys is the bash shell and common
utilities.
I think that we should avoid pointing Windows users towards MSys, lest
the mailing list turns into a "bash-help" or "unix-help" list.
I'm starting to regret that we didn't decide to move all of the
scripts to Python for 6.4.
I'm starting to regret that we didn't decide to move all of
the scripts to Python for 6.4.
I don't at all. Let's ship 6.4 and move dev focus to grass 7
instead of trying to turn grass 6.x into grass 7.x. WinGrass
may be a bit bumpy before we get there, but so be it.