error compiling glyph fonts #1237
Comments
|
Possibly related: #1235 |
|
I have noticed this aswell, however in my experience this doesn't affect the browsers's behaviour. Please confirm this actually causes an issue? |
|
It prevents the browser from rendering the glyphs completely. From what I’ve seen it isn’t simply the text editor not respecting the encoding, the character is re-written to the css output as ◻. Cheers, Mohit Gupta On May 27, 2015 at 11:30:09 AM, Michael Mifsud (notifications@github.com) wrote: I have noticed this aswell, however in my experience this doesn't affect the browsers's behaviour. Please confirm this actually causes an issue? — |
|
Can you produce a short example html + css. I'm failing to reproduce given the resources on their website |
|
Duplicate of #1231. |
|
Ok let me walk you through how I get to the error.
This is an excerpt compiled with Compass This is the same excerpt compiled using SASS Not sure if this is relevant but I'm using Sublime Text 3 and just in case I checked the css using TextEdit. |
|
This looks mildly suspicious. Haven't had time to look into it further. |
|
same issue here .glyphicon-plus:before { The result will omit the slash in libsass 3.2.5 |
|
fwiw I'm pretty sure you're missing your charset on your html document. Compare renderings of these two: <!doctype html>
<html>
<head>
<style>
div:after { content: '☃'; }
</style>
</head>
<body>
<div>test</div>
</body>
</html><!doctype html>
<html>
<head>
<meta charset="utf-8">
<style>
div:after { content: '☃'; }
</style>
</head>
<body>
<div>test</div>
</body>
</html> |
I attempted to use libsass (specifically python libsass) as a way to integrate Materialize css (http://materializecss.com) into my django stack.
I was simply using sassc to compile the materialize.scss file and libsass strips the content value out of the out going css.
Something that should compile to this
.mdi-navigation-menu:before{content:"\e8a1"}
Compiles to this
.mdi-navigation-menu:before {content: ; }
I've already brought this issue up in the python libsass git here, and we determined that the issue is likely with libsass.
If you have any other questions about how I found this error feel free message me for more details.
The text was updated successfully, but these errors were encountered: