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
yes, maybe you are right, at least with the second statement. Not many others seem to experience this behaviour like me..
Maybe as help for people who may run into this and read this page, is there a work-around like configuring the visual whitespace element to be sth. else ? Or so... if not its ok...
There's no way to reconfigure the whitespace character, and you'll run into other problems when the encoding of the library is mangled, so I'd look through my build process carefully to see where the problem is being introduced, and fix it.
wow finally! Found the source! After hours of checking everything else the reason was a missing utf-8 content type in s3 metadata which just showed up in production version. Thank you for the replies!
what should happen: normal whitespace shown
what happened: Â character shown instead of whitespace
what i tried:
<meta charset="UTF-8">
to htmlmy babel rc looks like this:

The text was updated successfully, but these errors were encountered: