Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.1.0a7
2020.3
2020.3.13f1
Issue ID
1348774
Regression
Yes
Certain Japanese typographic symbols break script when put in preprocessor directive
Reproduction steps:
1. Open the attached project "JapaneseTypography.zip"
2. Open scene "Scene"
3. Open "Test.cs" script
4. Input certain Japanese typographic symbols in a preprocessor directive (Examples: "～", "仝", "…")
5. Add "Test.cs" script to any GameObject
Expected result: Script compiles without errors
Actual result: Unable to add the script as component
Reproducible with: 2020.1.0a7, 2020.3.14f1
Not reproducible with: 2018.4.36f1, 2019.4.39f1, 2020.1.0a6, 2021.1.0a1, 2021.1.14f1, 2021.2.0b3
Note: Some typography symbols work, but not all.
Error: "Can't add script component 'Test' because the script class cannot be found. Make sure that there are no compile errors and that the file name and class name match."
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a1