Morten,
> What I propose is that the default values are
> translated, so if the user opens this dialog it will be displayed not
> as "General" but as whatever it is translated into.
OK. The problem is, when JabRefPreferences() is called,
Globals.setLanguage() is not called yet. I need to check th
Koji,
I think it will be very confusing for the users if the customized name
reads "General" in this dialog, and then is displayed in the chosen
language instead. What I propose is that the default values are
translated, so if the user opens this dialog it will be displayed not
as "General" but as
> reserved words. As a candidate, I chose to add "[[CUSTOM_TAB]]" to
> those keywords which is unlikely to become necessary for users.
I noticed those default keywords also appear in "Setting General
Field" dialog, so we may not have to attach such reserved words at
all, because there is no reason
Morten,
2011/5/17 Morten Omholt Alver :
> Perhaps
> we could translate the default names of the tabs, but if we translate
> whatever name the tab has at any time, it could be a little confusing
> for the user.
I see. So, if a user makes up a customized tab "Accept", it hits the
keyword "Accept" i
Koji,
I understand what you mean, but I think we have to solve it a bit
differently. The reason these tab names are not currently translated
is that the names and contents of these tabs are configurable. Perhaps
we could translate the default names of the tabs, but if we translate
whatever name th
Dear list,
I'm currently working on introducing Japanese interface to JabRef, and
on the way I noticed two things:
1) "General", "Abstract" and "Review" tabs in the entry editor are
not translated
2) The word "General" which appears in the above tab and the same
one in Preference need to
