language selection in Windows

[Lubomir I. Ivanov]

On 18 June 2013 18:01, Tomaz Canabrava <tcanabrava at kde.org> wrote:
> On Tue, Jun 18, 2013 at 11:57 AM, Dirk Hohndel <dirk at hohndel.org> wrote:
>> On Tue, 2013-06-18 at 17:46 +0300, Lubomir I. Ivanov wrote:
>>> > I don't think I like this. Command line arguments in general are not
>>> > user friendly at all. I'd much rather allow people to select the
>>> > language from the preferences and then store that selection in the
>>> > settings.
>>> >
>>>
>>> a UI preference is definitely better. it could use the locale language
>>> until the user picks a new one from an #ifdef section of the settings
>>> dialog, as this is only needed on Windows..
>>> for that we have to grab the list of folder names in share/locale, but
>>> the list may still look a bit weird without aliases. e.g. it_IT ->
>>> Italian.
>>
>> We should be able to just add the xx_YY -> text conversion somewhere in
>> our preprocessing
>>
>> /D
>>
>> _______________________________________________
>> subsurface mailing list
>> subsurface at hohndel.org
>> http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
>
> Just a quickie, I don't think this is needed only for windows.
> for example, I'm trying to learn french, so everything in my computer
> is french - but sometimes I cant understand something and like to do a
> quick language change. this is appreciated in other SO's as well.
>

in any OS this will probably require application restart, because
that's how gettext works AFAIK. while on windows the variable will
exist only for the application session (e.g. started from a desktop
shortcut), i'm not sure how well will that work on unix-like, as for
example we may have to store/override/restore environment variables
like $LANG/$LANGUAGE, but then if the user starts subsurface like:

subbsurface&

said terminal will remain with a modified variable if i'm not
mistaken, which may be a bit intrusive?

lubomir
--