Skip to content

Conversation

doamatto
Copy link
Contributor

Blocked by #123.

Resolves #61.
Resolves #39.
Resolves #5.

I'll undraft this PR once #123 is merged

gervasiocaj and others added 30 commits April 23, 2017 21:29
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"
Added comments to `i18n.js` on how to block unfinished translations from being published
Translation of the remaining questions
@doamatto
Copy link
Contributor Author

Rebasing to proper branch

@doamatto doamatto closed this Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

What about other languages? The Translated (zh-CN) version. Translation
5 participants