supper octopress spanish characters Ñ

[angelbotto]

Requested assistance to see how I may support octopress Spanish language characters like Ñ or tildes á é í ó ú

`read_yaml ': invalid byte sequence in US-ASCII (ArgumentError)

thanks in advance and sorry for my English

---

Solicito colaboracion para ver como hago posible que octopress soporte caracteres del idioma español como la Ñ o las tildes á é í ó ú

`read_yaml': invalid byte sequence in US-ASCII (ArgumentError)

[bhousel]

This should just work in YAML, as long as the file is saved with a UTF-8 encoding with a starting byte order mark.

Can you check your text editor and see how the file is saved?
For example in Sublime Text, under File menu, there is an option "Save with Encoding" and I can choose "UTF-8 with BOM".

[angelbotto]

mm nope, I also thought the same but still generates the same error.

http://dl.dropbox.com/u/27031193/error.png

thanks for helping

[imathis]

What editor is that you're using? Some editors do a poor job of supporting UTF-8. I helped someone over Twitter not that long ago who found that copy and pasting from a web page into Coda2 was causing mixed content even though Coda2 was supposed to be using UTF-8. Have you copied and pasted from somewhere? Can you create a simple post to test this further? I suggest generating a clean blog with a single post with the Ñ character as the content to isolate from other possible issues.

[angelbotto]

My editor is "sublime text2" realize a new post delete the old with the new character Ñ only and keeping with UTF8 encoding and still generates the same error: s

http://dl.dropbox.com/u/27031193/errorn.png

thanks for helping

[imathis]

Does replacing that Ñ with some other text else allow the site to generate just fine?

[angelbotto]

is curious, the genre once again raked new_post post [] I can save and edit without any inconvenience the problem is to encode it in utf-8

I once coded recognize any text.

[Neil-Smithline]

I think this is a Jekyll bug.

I had a mighty battle with it when I moved to Octopress. I posted about it. See the "Converting From Nanoblogger To Jekyll" section starting with the second paragraph.

I've submitted a pull request to Jekyll so that it provides better error messages but that doesn't fix the underlying bug. Perhaps there is a strategy for using a broader character set in Jekyll but I only speak English so I've not bothered to look for it.

[angelbotto]

Resolve the issue with this #144 adding these two environment variables

   export LC_CTYPE = en_US.UTF-8
   export LANG = en_US.UTF-8

thank you very much for your help :)

[angelbotto]

imathis wonderful tool, thanks.

[Neil-Smithline]

I updated the FAQ to include this information. Thanks for letting us know it worked @angelbotto

[imathis]

Thanks! Glad you've gotten it sorted :)