Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some menu & message items lack translation keys #289

Closed
koji33 opened this issue Nov 4, 2015 · 3 comments
Closed

Some menu & message items lack translation keys #289

koji33 opened this issue Nov 4, 2015 · 3 comments

Comments

@koji33
Copy link
Contributor

koji33 commented Nov 4, 2015

In l10n property files in HEAD, some translation keys are missing. On starting JabRef, we have following stderr (thus, we may have more which not appear on stderr):

Warning: could not get menu item translation for "Insert selected citations into %d" for locale ja
Warning: could not get menu item translation for "Groups" for locale ja
Warning: could not get message translation for "Check integrity" for locale ja
Warning: could not get message translation for "ADS from ADS-DOI" for locale ja
Warning: could not get message translation for "Save fields sorted in alphabetic order (as in versions 2.10+)" for locale ja
Warning: could not get message translation for "Save fields in unsorted order (as until version 2.9.2)" for locale ja
Warning: could not get message translation for "Save fields in user-defined order" for locale ja
Warning: could not get message translation for "HTML to LaTeX" for locale ja
Warning: could not get message translation for "Unicode to LaTeX" for locale ja

@koppor
Copy link
Member

koppor commented Nov 4, 2015

Regarding the 2.9.2 and 2.10+ entries: Depends on #116. We will check the others.

@oscargus
Copy link
Contributor

"Insert selected citations into %d", "HTML to LaTeX" and "Unicode to LaTeX" I have added, and I have definitely not done anything related to the translations (as I didn't understand how it worked at that time).

However, with the rather massive remake of the translations in #301 it may make sense to wait a bit and then introduce all new strings in one go.

@stefan-kolb stefan-kolb added this to the v3.0 milestone Nov 18, 2015
@matthiasgeiger
Copy link
Member

Fixed with #390.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants