Content
View differences
Updated by Jens Ulferts almost 11 years ago
Create the possibility to integrate more languages into core and community plugins so the user does not need to install a plugin for these languages.
**Acceptance criteria** This will be done the following way:
- A user installing OpenProject can switch to languages core: OpenProject-Translations will be in the application is translated to (e.g. german, french)
- Translations for core Gemfile and plugin are managed in [crowdin](https://crowdin.com/projects/opf)
- Projects for each exist
- With every release new translations are rolled out.
- Synchronization between github repo store and crowdin is automated. load all locales except english
- A user does not need to install a plugin.
- plugins: The existing german localization is locales will be stored and loaded in/by the plugins themselves
Updating the locales will be done once uploaded a day by our CI and new locales are pushed to crowdin to make use of the work invested there. After this, crowdin is the single source of truth for german, too.
**Out of scope**
Translating to other languages release/dev-branches.
**Acceptance criteria**
- A user installing OpenProject can switch to languages
- Translations for core
- Projects for each exist
- With every release new translations are rolled out.
- Synchronization between github repo
- A user does not need to install a plugin.
-
Updating the locales will be done
**Out of scope**
Translating to other languages