Easier way of changing language

Oscar Fuentes пишет:
> Public bug reported:
>
> I'll like to use bazaar explorer with English language, but it starts
> with Spanish (as this is a Spanish Windows XP box) and I was unable to
> find a configure option for switching to English.

Set environment variable LANG or LANGUAGE to en.

If this is not option for you then you can delete translations files
from explorer/locale directory.

Or poke us one more time about adding special config option (though Ian
don't like to add config options).

Alexander Belchenko <email address hidden> writes:

> Oscar Fuentes пишет:
>> Public bug reported:
>>
>> I'll like to use bazaar explorer with English language, but it starts
>> with Spanish (as this is a Spanish Windows XP box) and I was unable to
>> find a configure option for switching to English.
>
> Set environment variable LANG or LANGUAGE to en.
>
> If this is not option for you then you can delete translations files
> from explorer/locale directory.

This is okay with me, thanks.

> Or poke us one more time about adding special config option (though Ian
> don't like to add config options).

On software used by developers, where English is the "lingua franca",
defaulting to the local language may be the right thing to do as far as
it can easily switched to English. If I report a bug saying "go to menu
Herramientas -> Sombrero -> foobar" would it comprehensible to you? It
is reasonable to switch to English for describing the GUI elements
involved on the bug.

Apart from this, at least the Spanish translation is incomplete and some
words look inappropriate, IMHO, which is a bit annoying. I'm not
interested on fixing this because I don't want to use the Spanish
translation, and a translation that is fine for a Spaniard will be odd
for a Mexican.

--
Óscar

Oscar Fuentes пишет:
> Alexander Belchenko <email address hidden> writes:
>> Oscar Fuentes пишет:
>> Or poke us one more time about adding special config option (though Ian
>> don't like to add config options).
>
> On software used by developers, where English is the "lingua franca",
> defaulting to the local language may be the right thing to do as far as
> it can easily switched to English. If I report a bug saying "go to menu
> Herramientas -> Sombrero -> foobar" would it comprehensible to you? It
> is reasonable to switch to English for describing the GUI elements
> involved on the bug.

I'm using Russian translation (and trying to maintain it actually),
but when I need to report bug and/or make screenshot I'm usually
do in the console:

set LANG=C
bzr explorer .

etc.

> Apart from this, at least the Spanish translation is incomplete and some
> words look inappropriate, IMHO, which is a bit annoying. I'm not
> interested on fixing this because I don't want to use the Spanish
> translation, and a translation that is fine for a Spaniard will be odd
> for a Mexican.

Not so fast and not so hard, please. Language codes much more complex than just es (Spanish) or ru
(Russian).
GNU gettext supports country codes in addition to language codes, so

es_ES is the Spain Spanish
es_MX is the Mexico Spanish

See:
http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes
http://www.gnu.org/software/gettext/manual/gettext.html#Country-Codes

Oscar,

Is more required here beyond documentation on how to do this? We use an environment variable because Explorer calls out to lots of other programs and the majority of those understand LANG but don't take a well known option for passing the preferred language on.

Ian Clatworthy <email address hidden> writes:

> Is more required here beyond documentation on how to do this? We use an
> environment variable because Explorer calls out to lots of other
> programs and the majority of those understand LANG but don't take a well
> known option for passing the preferred language on.

In this case, I guess that documenting LANG is the only way, along with
suggesting that if the user really wants to force a language on explorer
without changing other locale parameters (decimal separator, date
format, etc) removing the translation files works.

--
Óscar

Hi all,

Sorry to get involved in the comments but it affects me also.

Me tried to install Bazaar 2.x in my PC and get the same problem, me very excited with the new (for me) Bazaar Explorer so me tried to test it and guess what? Spanish language. I usually prefer English language for development because it simplifies and makes it heterogeneous work multi-language work offices and also because it is easier to report problems as previous commenter said.

Although a developer is supposed to know how to set a environment variable (LANG procedure which i assume it is available also for windows) it is annoying to have to do that, because you must *know* that you must make it to work, and because it is a little uncomfortable. Linux users may be quite familiar with LANG, but Windows users not so much.

My opinion is that a combo in the GUI for language choosing is the right way, as it simplifies the usage for the user (it is ok to restart the application and then apply changes) and makes life easier :)

So, my two cents: another vote for the language change option GUI combo. ;)

David.

And another +1 for a language switcher back to English.

The half-translated German interface in git GUI has always annoyed me, and I hoped that Bazaar would be different.

As a developer I need to learn the English terms anyway, to report bugs, participate in discussions, google for help etc. There is little benefit in a translated interface, and by any means it should be optional and easy to switch to English. And this setting should be independent from other applications - I am happy to run my Office package in German.

Thanks!

Just want to add, deleting the locale files did the trick for me, but I would have expected this could be done with a GUI switch.

In the past I've proposed to introduce `language` variable for bazaar.conf, so it can be shared by all bzr clients, and used to set required user language. Once I will have some free time I will implement it with support in qbzr and bzr-explorer. If anybody else want to volunteer to do so, I will be happy to mentor this person.

What where the developers thinking, I mean really? Do you do quality checks on the translated language to check if it really is a good translation and not a bunch of gibberish? Because the Estonian translation I have is just horrible. I can't understand anything. It boggles the mind that Bzr developers thought all the translations are so good, that a simple access to changing the language would not be necessary.

Yes, the quality of some translations is below our optimistic expectations.

As a workaround you can just delete locale folder from the location where Bazaar Explorer installed.

With trunk revno 472 you can use Tools -> Options -> Appearance -> User Interface -> Language.