Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.1f1
Issue ID
1021628
Regression
No
Text file content encoded with ANSI won't show in the preview inspector if it contains Extended ASCII character
How to reproduce:
1. Create a text file containing any character present in second half of the "Windows-1252" character set (‡ for example)
2. Save the file using ANSI (Windows-1252) encoding
3. Add the text file to any project
4. Select the text file and look at Inspector window
Expected results: content of text file appears in the Inspector window
Actual results: Inspector window is empty
Reproducible with: 5.6.5p3, 2017.1.3p3, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0b13, 2018.2.0a7
Note: in versions 5.6.5p3, 2017.1.0b2 only the characters present in second half of the "Windows-1252" character set fail to print, other characters appear in the Inspector window
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
- Reflection Probe “adjusting number of stops to over or under expose the texture” setting does not update in Scene realtime
- UI Toolkit rendered text breaks when toggling FontWeight styles through code
- Transparent pixels are still hit when alphaHitTestMinimumThreshold is set to a non-zero value
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
This is a duplicate of issue #961349