Replies: 2 comments 1 reply
-
Interesting, do you know if this happened with a recent change? I don't remember seeing this previously. |
Beta Was this translation helpful? Give feedback.
1 reply
-
This was because I switched to a JSON5 library in a recent version of It does appear to be fixed with that change, thanks for letting me know! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
The main website at unsuckjs.com has become mojibaked. It is correctly served as utf-8 correctly but it seems there was an issue in how it was statically built; the text is utf-8 that has been incorrectly saved as
latin-1
/windows-1252
/iso-8859-1
.The issue appears under Chrome and Firefox, and you can confirm it's a mojibake issue by trying to decode the document as
iso-8859-1
instead ofutf-8
and observe that non-ascii text remains broken (but in a different way).It's not immediately obvious; only when you look at the names of projects that include non-ansi/ascii characters, e.g.
and
Verification of mojibake charsets:
Beta Was this translation helpful? Give feedback.
All reactions