Closed JBPressac closed 2 months ago
Are you seeing actual rendering problems associated with any of this?
Those are places specifying which iconfont characters to use, so they're supposed to be "weird" private-use characters that don't render as anything in source form.
I don't know where those icons are supposed to be displayed in the HTML pages and I did not found this problem because of HTML rendering problems. I did noticed it because the text editor I used to edit this file replaced the weird characters by a question mark. Besides those strange characters are in the GitHub source file.
In previous commit, the unicode characters corresponding to "weird characters" are correctly displayed (for instance, one is displayed \f0d9
). Which make me thing that the commit 'Edit theme styles against new public styles.' introduced an encoding problem in the source style.css file.
I don't believe this is an encoding problem. It's just how the compiler used on the CSS works: it changes the \f0d9
that we write in the .scss source styles into an actual Unicode character in the compiled .css file, because the character uses fewer bytes.
Hello,
Seems that there are encoding problems in style.css: