Skip to content

Conversation

@suluke
Copy link
Owner

@suluke suluke commented Mar 8, 2018

This is an effort to implement #79, i.e. i18n functionality.

Roadmap:

  • Allow for static html elements to be dynamically translated
  • Allow localization of dynamically created content
  • Allow localization of static html elements' attributes
  • Allow localization of dynamically created elements' attributes
  • Make display names and descriptions of effects translatable
  • Create translations for all static html text
  • Create translations for all effects' config dialogs
  • Persist the selected locale in the user's config (but without causing render pipeline rebuild)

suluke added 5 commits March 8, 2018 17:49
This commit adds a language picker component as well as a Localization-
Manager class which keeps a list of managed DOM elements to be translated
when the user changes the language. Only two locales (en_US and de_DE) have
been added so far (json files) and they only contain localized strings for
three small text components, so a lot of work still needs to be done. Also,
dynamically adding new dom nodes to be localized by the LocalizationManager
has not been used anywhere yet.

This work is done to eventually implement #79
This does not include invisible texts (such as title attributes).
This commit also moves the LocalePicker control into i18n.js
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.

2 participants