Greetings
I’m trying to translate the buttons in module’s interfaces (Run, Help, Copy, Stop) and I know that they are managed by GTK so it depends on the OS language. But, I really need to translate them so someone advised me to add labels to those butrtons. In which gui_module shall I do that?
Thanks
Helena
Greetings
I’m trying to translate the buttons in module’s interfaces (Run, Help, Copy, Stop) and I know that they are managed by GTK so it depends on the OS language. But, I really need to translate them so someone advised me to add labels to those butrtons. In which gui_module shall I do that?
Thanks
Helena
On Thu, Jul 21, 2011 at 11:01 AM, Helena Herrera
<helenaherrera1980@gmail.com> wrote:
Greetings
I'm trying to translate the buttons in module's interfaces (Run, Help, Copy,
Stop) and I know that they are managed by GTK so it depends on the OS
language. But, I really need to translate them so someone advised me to add
labels to those butrtons. In which gui_module shall I do that?
Devs, since this has been asked so often (incl. myself), I really
vote for i18n-tagging these buttons.
Any objections?
Markus
Hi,
2011/7/21 Helena Herrera <helenaherrera1980@gmail.com>:
I'm trying to translate the buttons in module's interfaces (Run, Help, Copy,
Stop) and I know that they are managed by GTK so it depends on the OS
language. But, I really need to translate them so someone advised me to add
labels to those butrtons. In which gui_module shall I do that?
what do you mean by "to add labels"? All buttons needs to have defined
labels, no need to "add". Do you mean tooltips or so?
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Hi,
2011/7/26 Markus Neteler <neteler@osgeo.org>:
Devs, since this has been asked so often (incl. myself), I really
vote for i18n-tagging these buttons.
is it really needed? It is good idea to leave it for underlaying
library to get standardized translation within given OS.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
On Tue, Jul 26, 2011 at 4:53 PM, Martin Landa <landa.martin@gmail.com> wrote:
Hi,
2011/7/26 Markus Neteler <neteler@osgeo.org>:
> Devs, since this has been asked so often (incl. myself), I really
> vote for i18n-tagging these buttons.is it really needed? It is good idea to leave it for underlaying
library to get standardized translation within given OS.
This will fail if a user wants a different language than that provided
by the OS. Me in Japan don't manage to read those buttons
easily in Japanese...
Markus
Markus Neteler wrote:
> > Devs, since this has been asked so often (incl. myself), I really
> > vote for i18n-tagging these buttons.
>
> is it really needed? It is good idea to leave it for underlaying
> library to get standardized translation within given OS.This will fail if a user wants a different language than that provided
by the OS. Me in Japan don't manage to read those buttons
easily in Japanese...
Translating the GRASS GUI won't help much if the rest of the desktop
is in Japanese.
And using a different language for portions of the GUI which are
high-level OS components (e.g. file selection dialogs) may not even be
possible.
--
Glynn Clements <glynn@gclements.plus.com>
On Wed, Jul 27, 2011 at 2:07 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
> > Devs, since this has been asked so often (incl. myself), I really
> > vote for i18n-tagging these buttons.
>
> is it really needed? It is good idea to leave it for underlaying
> library to get standardized translation within given OS.This will fail if a user wants a different language than that provided
by the OS. Me in Japan don't manage to read those buttons
easily in Japanese...Translating the GRASS GUI won't help much if the rest of the desktop
is in Japanese.
Sure, that's why there is a related ticket:
Add a "change language" option in GRASS GUI
http://trac.osgeo.org/grass/ticket/879
And using a different language for portions of the GUI which are
high-level OS components (e.g. file selection dialogs) may not even be
possible.
I had added it 1-2 years ago, it worked and it has been reverted since
then by someone else (which reintroduced the problem).
Markus