👍

I haven't had a chance to test the new version yet, but I trust your judgement, so :) Thanks again for looking into this, @XhmikosR !

I'd still like someone else to verify that the chcp 65001 hack isn't needed anymore.

See also https://github.com/juthilo/run-jekyll-on-windows/issues/6

Hmm, seems to me we still need to set the encoding in _config.yml (which is equivalent to chcp 65001).

I updated and replaced jekyll to/with v1.5.0 locally and when I removed encoding: UTF-8 from the config, I got the usual Liquid exception.

However, as Bootstrap users don't need to manually run any command (due to the encoding config), my suggestion would be to leave everything as is. I'll update my run-jekyll-on-windows guide, which we link to in the README and which is more suited for this kind of general information (the chcp part) IMO. Thoughts @mdo @cvrebert @XhmikosR ?

Yeah but that isn't the case with 1.4.3 where we had to do the chcp workaround even though encoding was set in configuration.

So at least now it respects that. IIRC version 2 has this completely fixed.

I removed that info from our Readme because for Bootstrap there's no need for it. You can add it in your guide of course.

From my tests I have yet to find a project that raises that exception with 1.5.0 apart from Bootstrap.
I'll dig into this more tomorrow but for bootstrap I don't think we need to add more apart from 1.5.0 being required.

I confirmed what I said above, even for Ratchet, which does not have encoding set in _config.yml, 1.5.0 works fine without the chcp hack.