• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows Notebad and Bush

If you have extra character sets you'll end up with something like this...

?????????

Anyone care to translate?
 
The reason this happens:

1) You are saving to 8-bit Extended ASCII (Look at the Save As / Encoding format)

2) You are reading as 16-bit UNICODE (You guessed it, look at the Save As / Encoding format)

This is why the 18 8-bit characters are being displayed as 9 (obviously not supported by your codepage) 16-bit UNICODE characters.

It's not magic, it's someone pretending to be a hacker by preying on the ignorance of others.

It's being read as:
0x4275
0x7368
0x2068
0x6964
0x2074
0x6865
0x2066
0x6163
0x7473

So much for this 🙁
 
After re-opening the file, I replaced the result with the original text it and saved it. When I opened it again, it read correctly. Nothing strange about strangeness in Microsoft programs. 😛
 
Originally posted by: Harvey
After re-opening the file, I replaced the result with the original text it and saved it. When I opened it again, it read correctly. Nothing strange about strangeness in Microsoft programs. 😛

.999999999999999999999999999999999999999999999999999999999999999999 😉
 
Back
Top