jekyll serve -w gives "invalid byte sequence in US-ASCII"

[guidobouman]

Trying to run jekyll to work on docs but can't get it to boot. There's UTF characters in a blog post which jekyll (ruby probably) does not like.

Tried setting the lang variables already:

LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"

No luck yet.

[vjeux]

Does it indicate where the utf8 characters are?

Christopher "vjeux" Chedeau
Facebook Engineer
http://blog.vjeux.com/

On Nov 15, 2013, at 2:42 AM, Guido Bouman [email protected] wrote:

Trying to run jekyll to work on docs but can't get it to boot. There's UTF characters in a blog post which jekyll (ruby probably) does not like.

Tried setting the lang variables already:

LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
No luck yet.

—
Reply to this email directly or view it on GitHub.

[zpao]

Quite possibly from my name - ’ (that's a real apostrophe, not the '). I've had that problem in the past.

What version of Ruby are you using? Like I said, I've had the problem in the past, but not recently (using 1.9.3 here). I think you're going to need at least 1.9.2 (see #401) anyway, so hopefully it's not a big problem.

Does it say which post? That would help narrow it down.

[guidobouman]

Sorry guys, rather incomplete error report.

Error takes place in: react/docs/_posts/2013-07-02-react-v0-4-autobind-by-default.md

Just a stacktrace until jekyll's scan method, no line numbers afterwards.

➜  docs git:(master) ✗ rbenv version
2.0.0-p247 (set by /Users/Guido/.rbenv/version)

bundle install and npm install ran without issues.

EDIT:
I can confirm that an em-dash was the cause of the error, but replacing it with a bare dash raised the error in another post. This should not be happening, as my ruby should just accept utf-8. Weird stuff...

[guidobouman]

Wow, I've been asleep this morning. I completely forgot export in front of my language statements. Found out when checking locale.