Localization issue
Raymond Martin
While in the process of trying to improve the localization support in the
program I have come upon an issue.
I have managed to make the keyboard shortcuts localizable. That is, depending
on your systems locale/language, or just preferred locale to use while running
OmegaT+, you can have different keyboard shortcuts than the defaults (US
English based).
The issue is that it might be that many applications, even properly/fully
localized, in a particular language may just be using the defaults instead
of specific ones for the particular language/locale.
It is hard for me to check the expected situation for numerous different
default locales. Thus, a little feedback from those of you working in non-US
default locales is needed. Could some of you please check the shortcuts you
are seeing in other applications (in your default non-US/English locales)
against those in OmegaT+ and report the differences for the "corresponding"
menu entries.
Any feedback on this is appreciated.
Regards,
Raymond
Silvermoon
I don't understand. Do yo want us to check if our Omegat+ versions
still use the default shortcuts or do you want us to tell you the
corresponding shortcut for each language?
If it's the latter, here are some shortcuts for Spanish:
nuevo ctrl+N
abrir ctrl+A
salir ctrl+Q
guardar ctrl+G
deshacer ctrl+Z
rehacer ctrl+Y
cortar ctrl+X
copiar ctrl+C
pegar ctrl+V
buscar ctrl+B
By the way: what is the difference between the first three entries of
the document menu and the corresponding entries in the project menu
(open vs. open project, new vs. new project, close vs. close project).
They do the same (as far as I can tell).
Raymond Martin
> I don't understand. Do yo want us to check if our Omegat+ versions
> still use the default shortcuts or do you want us to tell you the
> corresponding shortcut for each language?
>
>
> If it's the latter, here are some shortcuts for Spanish:
>
>
> nuevo ctrl+N
> abrir ctrl+A
> salir ctrl+Q
> guardar ctrl+G
> deshacer ctrl+Z
> rehacer ctrl+Y
> cortar ctrl+X
> copiar ctrl+C
> pegar ctrl+V
> buscar ctrl+B
By default the application uses the English shortcuts, no matter what language
you are in. These may or may not be what you want, or what is appropriate
to your particular locale/language. Unfortunately, I am not familiar with what
the settings might be across all languages and it is easier to get feedback
about this matter so that a decision can be made as whether to keep the
defaults or set up different ones for each locale.
In any event, I have altered the program so that a user "could" change these
if desired by editing the localization for their language.
>
>
> By the way: what is the difference between the first three entries of
> the document menu and the corresponding entries in the project menu
> (open vs. open project, new vs. new project, close vs. close project).
> They do the same (as far as I can tell).
No difference, just duplicates. The Document menu is like the File menu
that you find in many applications. The entries in those menus do not
all correspond to actually working with files. Some do and others are more
generic, like having New, Open, Close and similar. In the case of OmegaT+,
these three items apply to a project, but they could apply to other things
later on. For instance, I just started toying with launching the browser from
OmegaT+ (that you suggested doing), so I added an Open submenu to list related
things.
Regards,
Raymond
Silvermoon
is a perfect solution, you don't have to worry about the locales and
people can customize it at will.
I understand the menu duplicate thing now. If we want to open html
files, and other kinds of files, it's best to have a menu for dealing
with files in a sepparate fashion.
I see you are working on some of the ideas I gave, thanks. You listen
to what one says, other projects just disregard comunity feedback.
Raymond Martin
>
> I see you are working on some of the ideas I gave, thanks. You listen
> to what one says, other projects just disregard comunity feedback.
I do listen. At the same time, I don't always agree. But when I don't I
take the time to try to explain, at least minimally, why something
won't or can't be done (e.g., at a specific point in time).
So don't take it personally if I don't get to everything you'd like.
If I fail to explain, just ask and I will do my best to clarify my
reasoning.
Cheers,
Raymond
Tamás
Working on the Hungarian translation I also found a localization
problem regarding the keyboard shortcuts.
In the Alt+Up, Ult+Down, Alt+Right keyboard shortcuts Up/Down/Right
cannot be localized. These are the names of the arrow buttons on the
keyboard, they have local names. When I translate the appropriate
segments and generate the translations, the related hotkeys in the
Segment menu disappear.
Any idea?
Cheers,
Tamás
laseray
On Nov 26, 10:27 am, Tamás <locali...@gmail.com> wrote:
> Hi!
>
> Working on the Hungarian translation I also found a localization
> problem regarding the keyboard shortcuts.
>
> In the Alt+Up, Ult+Down, Alt+Right keyboard shortcuts Up/Down/Right
> cannot be localized. These are the names of the arrow buttons on the
> keyboard, they have local names. When I translate the appropriate
> segments and generate the translations, the related hotkeys in the
> Segment menu disappear.
>
> Any idea?
>
translation along with commands for setting the shortcuts inside the
localization files. This is a recent addition with 1.0.M3.
You cannot localize the text in those segments, e.g., alt + DOWN,
because it is being used in the program to assign a shortcut that only
the Java programming language understands. Which means it does not
understand anything other than English. The only way for these
shortcuts to show up localized at this time is for the default locale
of your operating system to correspond to locale support within Java.
Thus, if your default locale is Hungarian, for instance, and you start
OmegaT+, then the shortcuts will be in Hungarian, if Java actually has
default locale strings to support it. If it does not then you are out
of luck at this time.
What is the default locale of your OS when you start the program?
Raymond
P.S. If you want to change the shortcuts to something else (regardless
of final language) then you have to look at the Java API (Javadoc)
available online from Sun to see the allowed keys.
Tamás
I am using a Hungarian Windows XP and these shortcuts are in English.
I already translated some other products, coded in a different
language than Java (C++, I think) and in these language files such
shortcuts were localizable.
Unfortunately these shortcuts remain untranslated in OmegaT+, that's
why I submitted here this issue :)
Cheers,
Tamás
Raymond Martin
> I am using a Hungarian Windows XP and these shortcuts are in English.
> I already translated some other products, coded in a different
> language than Java (C++, I think) and in these language files such
> shortcuts were localizable.
strings should be there for these user interface components.
> Unfortunately these shortcuts remain untranslated in OmegaT+, that's
> why I submitted here this issue :)
programmatic features (keyboard shortcut strings ) is missing from Java
itself. I will try to check at Sun for exactly what locales are supported, but
I know for sure that it only covers a limited number of languages.
The only way to get these fixed is to have them added into the core of the
Java programming language itself. Something that might be possible depending
on how much you really want it. You would have to go to Sun or the OpenJDK
projects, for instance.
Raymond