Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.3f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1169358
Regression
No
Japanese diacritic symbols are missing from the build executable file when building the project
How to reproduce:
1. Open the attached project ("case_1169358-Unity_Japanese_Turbidity_point_Error_Test_Project.zip")
2. Open Project Settings
3. Inspect the project's name
4. Build the project
5. Inspect the project's build executable file name
Expected results: Project's name and the executable name match (the executable is named "がぎぐげごばびぶべぼぱぴぷぺぽ")
Actual results: Project's name and the executable name does not match (the executable is named "かきくけこはひふへほはひふへほ")
Reproducible with: 2017.4.30f1, 2018.4.4f1, 2019.1.11f1, 2019.2.0b10, 2019.3.0a9
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note (fix version 2019.3):
Fixed in 2018.4.13f1, 2019.2.9f1, 2019.3.0a12