-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue when using unicode in variables #52
Comments
Font-awesome although is in fact awesome, is massive. We're not using every single icon, in fact, we're using only 4 out of 675... It's unreasonable to keep using it. We're preparing our own font and styling, to keep the same approach, with much less MB to be loaded. It also, fixes the issue with [go-libsas][1] we're having, allowing us to move forward with the application. [1]: wellington/go-libsass#52
Font-awesome although is in fact awesome, is massive. We're not using every single icon, in fact, we're using only 4 out of 675... It's unreasonable to keep using it. We're preparing our own font and styling, to keep the same approach, with much less MB to be loaded. It also, fixes the issue with [go-libsas][1] we're having, allowing us to move forward with the application. [1]: wellington/go-libsass#52
Font-awesome although is in fact awesome, is massive. We're not using every single icon, in fact, we're using only 4 out of 675... It's unreasonable to keep using it. We're preparing our own font and styling, to keep the same approach, with much less MB to be loaded. It also, fixes the issue with [go-libsas][1] we're having, allowing us to move forward with the application. [1]: wellington/go-libsass#52
That is annoying. I don't believe go-libsass is causing this issue, but I'm taking a look |
Also thanks for posting a fully working, reproducible unit test. You are the best 💯 🎆 |
So interesting, the Ruby Sass maintainers seem to be resistant to address this problem which cropped up in a minor release of 3.4. You can force the expected ascii output by doing this: https://www.sassmeister.com/gist/22743e406eeb3744988c If possible, I'd recommend moving away from storing escaped unicode in variables. It's unlikely Sass will remedy this issue. There's no work been done to let developers dictate the encoding of Sass output. Long story here: sass/sass#1395 |
This may work as well, |
Nice research work. Thanks :) It's weird, as the same code worked totally fine with gulp/grunt. I doubt that the need of modifying an external library (like I've worked around the issue by not using I'm happy for the issue being resolved, as it is clearly not related to the package itself. Thanks again for investing time in this! |
@drewwells |
What
I stumbled upon an issue, where a unicode character that is in a variable, will not be compiled properly, but turned into a square instead.
It's particularly annoying, when working with sprites or something like
font-awesome
.Test case
Output
The text was updated successfully, but these errors were encountered: