-
Notifications
You must be signed in to change notification settings - Fork 92
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
Sass fails to read utf8 encoded files #86
Comments
Since your using @import the directive will not be adhered to your in ruby code land now and that has different criteria for file loading... You really need to force the ruby runtime character encoding to utf-8 Sent from my iPhone
|
Sorry, I guess I didn't clarify. With or without |
You might try the latest version of sass it uses Libsass now |
I'll give that a try next Monday; workstation is inaccessible this week. |
Okay, so I have some fascinating results... I took revision f4bbe67 and compiled it locally, as well as tested the publish
Here's a possibly relevant stacktrace (from the jsass stuff) from adding a BOM to the imported styles.css and removing the
|
got this fixed for new release |
I outlined the problem on StackOverflow, copied here.
I'm running on windows (currently development mode). I've also tested with 2.8.1 (latest on maven) to the same problem.
I have a
.scss
file (encoded utf8) with this binary data (this is a specific example, there are more unicode characters in the file):Which is the character
“
(left-quote).The file gets included (by
@import
directive, not the asset-pipeline directive, but both methods fail to read it correctly) in another file, and when fetching the result, I get this binary data:Which are the characters
“
Gradle build file has:
(not sure if there are any other relevant entries)
I made a reproduction case (latest default configurations): Wolvereness/Grails-Sass-Unicode-Test
Solutions that have not worked:
@charset
in either/both files-Dfile.encoding=UTF-8
ongrails
or therun-app
command//=encoding utf-8
at the top of the file(s)I did further investigation, and found that
-Dfile.encoding=windows-1252
is being forced as a JVM parameter on my system. However, asset-pipeline should ignore that when the file explicitly specifies@charset
or//= encoding
, and plausibly because of the sass specification that will default to assume utf8 when not otherwise specified.The text was updated successfully, but these errors were encountered: