Content
View differences
Updated by Marc Alcobé 9 months ago
**As** a mobile app user
**I want the** translations in the app to be consistent with the translations in the web interface
**so that** I get easily map the concepts between both worlds.
### **Acceptance criteria**
* [ ] The mobile app will be now available in multiple languages, as their translation strings for the web app are very advanced (higher than 90%), the first accepted ones will be:
* [ ] English
* [ ] German
* [ ] French
* [ ] Spanish
* [ ] Chinese Traditional
* [ ] Chinese Simplified
* [ ] Portuguese, Brazilian
* [ ] Korean
* [ ] Portuguese
* [ ] Polish
* [ ] Italian
* [ ] Ukranian
* [ ] Russian
* [ ] Japanese
* [ ] The order of the languages should be alphabetical as in the web app in the original language.
* [ ] By default the apps uses the language settings defined on the mobile device.
* [ ] If this language does not exist the fallback is English.
English
* [ ] We use the same translation strings we use for the web application
* [https://github.com/opf/openproject/tree/dev/config/locales/crowdin](https://github.com/opf/openproject/tree/dev/config/locales/crowdin)
* [https://crowdin.com/project/openproject](https://crowdin.com/project/openproject)
* There is an entry in the account settings to select any of the languages available.
### **Technical notes**
* [ ] Steps to have multi-language available:
* [ ] \[Manager\] A new project will be created inside of Crowdin for the mobile app.
* [ ] \[Developer\] Connect the flutter app strings to the project with the Flutter-Crowdin library.
* [ ] \[Manager\] Will use the the global "Translation Memory" function of Crowdin to populate the strings.
* [ ] \[Developer\] Ensures that the app uses the Crowdin strings properly.
### **Permissions
**Figma and visibility considerations** visuals**
Everyone should be able to change the language of the app.
### **Visual reference**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:320px;" src="/api/v3/attachments/781047/content">
### **Out of scope** https://www.figma.com/design/arGHBRVi6WLJDLTv0YoOoo/Mobile-App---Spike?node-id=1135-267645&t=xi3CAOiSg42CS7Ei-4
**I want the** translations in the app to be consistent with the translations in the web interface
**so that** I get easily map the concepts between both worlds.
### **Acceptance criteria**
* [ ] The mobile app will be now available in multiple languages, as their translation strings for the web app are very advanced (higher than 90%), the first accepted ones will be:
* [ ] English
* [ ] German
* [ ] French
* [ ] Spanish
* [ ] Chinese Traditional
* [ ] Chinese Simplified
* [ ] Portuguese, Brazilian
* [ ] Korean
* [ ] Portuguese
* [ ] Polish
* [ ] Italian
* [ ] Ukranian
* [ ] Russian
* [ ] Japanese
* [ ] The order of the languages should be alphabetical as in the web app in the original language.
* [ ] By default the apps uses the language settings defined on the mobile device.
* [https://github.com/opf/openproject/tree/dev/config/locales/crowdin](https://github.com/opf/openproject/tree/dev/config/locales/crowdin)
* [https://crowdin.com/project/openproject](https://crowdin.com/project/openproject)
*
### **Technical notes**
* [ ] Steps to have multi-language available:
* [ ] \[Manager\] A new project will be created inside of Crowdin for the mobile app.
* [ ] \[Developer\] Connect the flutter app strings to the project with the Flutter-Crowdin library.
* [ ] \[Manager\] Will use the the global "Translation Memory" function of Crowdin to populate the strings.
* [ ] \[Developer\] Ensures that the app uses the Crowdin strings properly.
### **Permissions
**Figma
Everyone should be able to change the language of the app.
### **Visual reference**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:320px;" src="/api/v3/attachments/781047/content">
### **Out of scope**