Fixed non-ASCII characters issue

[willian]

I'm developing an AngularJS project using gulp with gulp-ruby-sass in order to compile all the scss files. Everything worked on my machine (I have a MackBook Air, but I'm developing using Vagrant VM with Ubuntu), but when I tried to deploy it on Heroku I got:

Error in plugin 'gulp-ruby-sass'
Message:
    error /tmp/build_abab9a195c7b2366a08c918fe16ba4d5/bower_components/neat/app/assets/stylesheets/grid/_row.scss (Line 1: Invalid US-ASCII character "\xE2")

Here is the full output: https://gist.github.com/willian/673ce685f5200a93ac2d

The problem is with some non-ASCII characters in some files. I'm creating this PR to fix those files by removing non-ASCII characters.

If you want to know how I found those characters, I open the files on my Vim and I executed /[^\x00-\x7F]

PS.: I'm sorry, I updated the version because I wasn't able to test only by pointing to a commit hash.

[tysongach]

If I’m understanding correctly, the error is isolated to _row.scss (looks like an en-dash was used), so the other four files you edited shouldn’t need to be changed; especially the README.md.

Also, fine to do a version bump for your own testing, but can you remove that from the PR and squash all commits down to one?

[willian]

Hi Tyson, yes, I will do that right now.

[willian]

@tysongach Done, PR is fixed.

[tysongach]

@willian Looks like the README.md is still changed.

[foxx]

Just ran into this problem, thought I was going insane.

[willian]

@tysongach fixed =)

[tysongach]

@willian Thanks! Can you do me a favor?

Can you add @charset "UTF-8"; to the very top of _row.scss and try again (without changing the hyphens)?

[willian]

@tysongach Yes, I can do that.

[rbngzlv]

I also ran into this problem.

Adding @charset "UTF-8"; to the very top of the file, without changing the hyphens, as suggested by @tysongach also fixed the issue.

Can confirm this @willian?

[aleciafb]

Adding @charset "UTF-8"; to the top of grid/_row.scss fixed the issue here too.

[mzgajner]

It would still be very nice if this is fixed in Neat itself (either by adding the charset declaration or by replacing the dashes) - I usually install it with bower or npm and having to manually change the file after this prevents (elegant) automatic builds.