Text encoding glitch - being set to unicode without setting the encoding

Subscribers:
14,200
Published on ● Video Link: https://www.youtube.com/watch?v=aXfHrILDf88



Duration: 6:46
1,319 views
36


https://www.patreon.com/ulillillia --- While working on trying to get the new text parsing system up and going, I encountered a very strange glitch that I wasn't expecting to see at all. I thought my file was corrupt. So, I dig out the hex editor to check and it's actually still completely in tact, exactly the way I had saved it before. By using the hex editor to change one byte, the very first byte, I was able to restore the file. Whether I use the hex editor to set that first byte to 0xFE, or I use Metapad or even the built-in Notepad, I get exactly the same problem. But, change that first byte to something that isn't the 0xFE and it works just fine. I was intending on having the 0xFE byte instruct my text parsing function that it needs to copy the hero/main character's name at this location (they're user defined). My own program reads the 0xFE byte properly, along with the rest of the text so my own program is doing better than Metapad and Notepad. What is going on here to cause this to happen and how do I get either Metapad or Notepad to display the text properly? It saves and updates properly while it's displayed correctly, but if I close the file and reopen it, it's glitched.







Tags:
ulillillia
baricanna