Localization #123
Localization #123
Conversation
Uses the i18next framework. Resolves #5
Progress of adaptation: - [x] Questions - [x] Quiz - [ ] Index - [ ] Instructions - [ ] Results
Progress of adaptation:
- [x] Questions
- [x] Quiz
- [x] Index
- [x] Instructions
- [ ] Results
Progress of adaptation: - [x] Questions - [x] Quiz - [x] Index - [x] Instructions - [x] Results
In order to load the namespaces and do the string binding, just load the i18n.js file on the HTML and call the i18n_load_ns with the namespaces notation found [here](http://i18next.com/translate/namespace/). To fill the string data (e.g. "12 apples), the element must adhere to the following notation (see HTML data-* attributes): ```html <p data-i18n="apple_count" data-amount="18"></p> ``` ```json { "apple_count": "{{amount}} apples" } ``` To refresh the string, alter the data-* attribute accordingly and call `i18n_ready()`.
…lation Corrections according to the ortographic agreement and changes on the master branch
To localize images, add the file-[lng].svg to the value_images/ diretory and add an entry on the corresponding translation.json:
"file.svg": "file-[lng].svg"
This reverts commit 144b16c.
Added comments to `i18n.js` on how to block unfinished translations from being published
This reverts commit f7fe42b.
Translation of the remaining questions
Spanish translation, thanks to @locoluis
|
don't let the project die @gervasiocaj |
|
Hi, I made a Japanese translation. |
|
Hey @choux-kasa, that looks great! I'll look into adding these into my fork of the project to check it's all OK. In future I'd suggest learning to use git, because it makes the process a lot easier, but thanks for the translation. |
|
I can contribute FR-FR locales |
Co-authored-by: Guillaume de Sagazan <guillaume@desagazan.fr>
Add French and Japanese locales
|
Hello, popping out randomly; any way for the general public to assist the maintainers in getting this merged? :-) |
|
Absolutely! You can fork the project and contribute translations via a pull request into the If you're less well-versed in git & github, then feel free to post your translation here in this comment section and either me or one of the other lovely people who contribute to the project will get round to applying it to the codebase! 😄 |
|
Thank you for your nice, inclusive reply. I think I can manage git and GitHub, and the language I can translate is aready baked into this PR, so I was wondering what I could do to ease the path of this PR. I'll try to resolve merge conflicts :-) |
This pull request replaces #14 and includes more recent commits to the repo.
Work that still needs to be done before this can be merged:
master.