You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the file being encoding is anything than UTF-8-RAW (and maybe UTF-16-RAW), it will encode the file for console releases.
"-RAW" is how autohotkey recognizes the format, which is the language I'm the most familiar with. It's also just simple Little Endian without BOM.
Basically, if it detects BOM, it'll go "nope, not for PC"
This issue primarily comes up because some text editors, such as those that come built into Windows, will overwrite the encoding.
Some editors can handle editing in this encoding, but some such as Notepad++ can't convert a file over to it (despite being able to convert to other encodings otherwise)
What would be ideal is if there was a flag that could be set to specify platform to avoid this issue.
The text was updated successfully, but these errors were encountered:
If the file being encoding is anything than UTF-8-RAW (and maybe UTF-16-RAW), it will encode the file for console releases.
"-RAW" is how autohotkey recognizes the format, which is the language I'm the most familiar with. It's also just simple Little Endian without BOM.
Basically, if it detects BOM, it'll go "nope, not for PC"
This issue primarily comes up because some text editors, such as those that come built into Windows, will overwrite the encoding.
Some editors can handle editing in this encoding, but some such as Notepad++ can't convert a file over to it (despite being able to convert to other encodings otherwise)
What would be ideal is if there was a flag that could be set to specify platform to avoid this issue.
The text was updated successfully, but these errors were encountered: