Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2023.2.0a16
2023.3.0a3
Issue ID
UUM-37674
Regression
No
Japanese string with ":" not serialized properly using localization package
- Create a new project with localization package
- Create a string table with the following string:
改造アイテムがありません
ID: \{0}
モッド名: \{1}
Mod guid: \{2}
Actual result: Console error appears Unable to parse file Assets/Test Table_ja-JP.asset: [Parser Failure at line 32: Expect ':' between key and value within mapping]
and the string is serialized as
"\u6539\u9020\u30A2\u30A4\u30C6\u30E0\u304C\u3042\u308A\u307E\u305B\u3093\nID:
{0}
\n\u30E2\u30C3\u30C9\u540D: \{1}\nMod guid: \{2}"
Editor: 2020.3.38f1
com.unity.localization: 1.4.3
See more info in attached project and forum post -
[https://forum.unity.com/threads/very-weird-bug-related-to-unitys-serialization.1418131/]
h4.
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.