Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a3
2019.3.0b2
Issue ID
1183390
Regression
Yes
Editor is not fully translated to English when changing the language from any of the available APAC languages back to English
How to reproduce:
1. Install a Unity version using Unity Hub
2. In the Unity Hub go to 'Installs'
3. Click on the three dots next to the installed version and select 'Add Modules'
4. Install any available (APAC) language pack
5. Create and open a new Unity project
6. Open 'Preferences' window and select 'Languages' tab
7. Change the Editor's language to the installed language
8. Change the Editor's language back to English
Expected result: Editor is fully translated back to English
Actual result: Editor is not fully translated back to English and some parts are still in the installed language
Reproducible with: 2019.3.0a3, 2019.3.0b5
Not reproducible with: 2018.4.10f1, 2019.2.7f2, 2019.3.0a2
Could not test with: 2017.4.32f1, 2020.1.0a1, 2020.1.0a7 (Language packs not available)
Additional note: re-opening the project will result in the Editor being completely translated back to English
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note (2020.1.X):
Low priority defect and unlikely to be fixed for the near future.