Search Issue Tracker
Fixed
Votes
0
Found in [Package]
0.8.0-preview
Issue ID
LOC-126
Regression
Yes
[Localization] "No Translation Found Format" variable isn't used when an Entry Locale is empty
How to reproduce:
1. Open the user's attached "Test localization package 2" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
Expected results: In the Game view both "-------" text fields become "No translation found for 'Entry 1'"
Actual results: In the Game view both "-------" text fields become empty
Reproducible with: 0.8.0-preview, 0.9.0-preview (2019.4.15f1, 2020.1.14f1, 2020.2.0b12, 2021.1.0a6)
Not reproducible with: 0.7.1-preview (2019.4.15f1, 2020.1.14f1, 2020.2.0b12, 2021.1.0a6)
Notes:
- Changing languages can produce a broken variation of the No Translation Found Format text (can be seen when switching to the Spanish language in the user's project)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment