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

Interface translations #451

Open
2 of 3 tasks
BeritJanssen opened this issue Mar 31, 2021 · 2 comments · Fixed by #513
Open
2 of 3 tasks

Interface translations #451

BeritJanssen opened this issue Mar 31, 2021 · 2 comments · Fixed by #513
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@BeritJanssen
Copy link
Member

BeritJanssen commented Mar 31, 2021

  • Get translations of interface elements
  • Add translations to interface
  • Enable user to switch language (rather than just auto-detect)
@BeritJanssen BeritJanssen added the enhancement New feature or request label Mar 31, 2021
@BeritJanssen BeritJanssen added this to the Extra mile milestone Mar 31, 2021
@jgonggrijp jgonggrijp self-assigned this Mar 31, 2021
@jgonggrijp
Copy link
Member

@jgonggrijp jgonggrijp linked a pull request Nov 30, 2021 that will close this issue
jgonggrijp added a commit that referenced this issue Mar 15, 2022
Adding these changes here as part of #517 instead of in #513 because
the latter is outdated compared to the former with regard to these
templates.

@JeltevanBoheemen FYI
jgonggrijp added a commit that referenced this issue Mar 15, 2022
Some parts of some templates seem to have previously escaped attention,
especially placeholder, data-tooltip and aria-label attributes. Besides
those, there were some changes that were added in parallel on develop,
as well as a few pieces where alternative orthography or sentence
structure of other languages needed to be taken into account.
jgonggrijp added a commit that referenced this issue Mar 16, 2022
Adding these changes here as part of #517 instead of in #513 because
the latter is outdated compared to the former with regard to these
views. This is a follow-up on the previous commit, which regarded the
templates.

@JeltevanBoheemen FYI
jgonggrijp added a commit that referenced this issue Apr 20, 2022
In their infinite wisdom, the i18next-parser team decided to go ESM-
only, which obviously doesn't work with a TS gulpfile that is still
emulating ESM on top of CommonJS. Sigh.
jgonggrijp added a commit that referenced this issue May 2, 2022
This also adds dynamism so that the translation strings cannot be
requested before they are available.
jgonggrijp added a commit that referenced this issue May 2, 2022
The underscore is the context and number separator in i18next. At the
time of writing we are not using this anywhere yet. To avoid confusion,
use a dash as a word separator.
jgonggrijp added a commit that referenced this issue May 2, 2022
i18next-parse is stateful. Apparently, the contents of the
translation_old.json are taken into account, too.
@jgonggrijp
Copy link
Member

Reopening because the user-controllable language switch hasn't been implemented yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants