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

Fix #49: Add additional Japanese localization strings provided by toshiakikoike #539

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

kden
Copy link

@kden kden commented Jun 21, 2016

This pull request is Finalized

Related issue(s) and/or pull request(s)

#49

Test cases, sample files

My Japanese is rusty, so I validated each new string by looking it up in Google translate and making sure that it was at least a reasonable approximation of the English version (and not, for example, Spam.)

I had to test in Firefox because for some reason the navigator.userLanguage was undefined and navigator.language was en_US in Chrome (Ubuntu 14.04), even though I set my browser preferences to Japanese. In Firefox, I could see and confirm some of the new strings under the Settings->Style menu and they looked fine.

Additional information

@rkwright rkwright changed the title #49 Add additional Japanese localization strings provided by toshiakikoike Fix #49 Add additional Japanese localization strings provided by toshiakikoike Jul 5, 2016
@rkwright rkwright changed the title Fix #49 Add additional Japanese localization strings provided by toshiakikoike Fix #49: Add additional Japanese localization strings provided by toshiakikoike Jul 5, 2016
@danielweck
Copy link
Member

Hello,
thank you very much for your contribution. Do you have time to compare with the latest i18n messages in the develop branch? I think there are 2 or 3 new labels to translate.
We will review the pending language contributions to merge them as soon as possible.
Kind regards, Daniel

@kden
Copy link
Author

kden commented Feb 16, 2022

Is there still interest in having this done, or should I close it out?

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

Successfully merging this pull request may close these issues.

2 participants