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 4th officially supported OpenProject languages + Ukranian: web app are very advanced (higher than 90%), the first accepted ones will be:
* [ ] English (base strings)
* [ ] German
* [ ] French
* [ ] Spanish
* [ ] Chinese Traditional
* [ ] Chinese Simplified
* [ ] Portuguese, Brazilian
* [ ] Korean
* [ ] Portuguese
* [ ] Polish
* [ ] Italian
* [ ] Ukranian
* [ ] Once the main languages are added we will check which is the amount of competition for other languages, specially the ones at around 90% competition on the web app.
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.
* [ ] There is an entry in the account settings to select any of the languages available.
### **Technical notes**
* [ ] _\[open\] Do we download the translation strings from Crowdin on app opening or on new version? Preferred on app opening but need to check the complexity._
* [ ] 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 and visibility considerations**
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**
**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
* [ ] English (base strings)
* [ ] German
* [ ] French
* [ ] Spanish
* [ ]
* [ ] Chinese Simplified
* [ ] Portuguese, Brazilian
* [ ] Korean
* [ ]
* [ ]
* [ ] Italian
* [ ]
* [ ]
* [ ] By default the apps uses the language settings defined on the mobile device.
* [ ] If this language does not exist the fallback is English.
* [ ] There is an entry in the account settings to select any of the languages available.
### **Technical notes**
* [ ] _\[open\] Do we download the translation strings from Crowdin on app opening or on new version? Preferred on app opening but need to check the complexity._
* [ ] 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 and visibility considerations**
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**