Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

1297 host jekyll content #33

Merged
merged 9 commits into from
Aug 4, 2014
Merged

1297 host jekyll content #33

merged 9 commits into from
Aug 4, 2014

Conversation

morty
Copy link
Contributor

@morty morty commented Aug 4, 2014

This is working now, but due to encoding issues the Jekyll site won't compile until my pull request has been merged:

UKGovLD/ukgovldwg#70

davidread pushed a commit that referenced this pull request Aug 4, 2014
@davidread davidread merged commit 9777577 into master Aug 4, 2014
@davidread davidread deleted the 1297-host-jekyll-content branch August 4, 2014 16:41
@davidread
Copy link
Contributor

Now we're on rvm can we switch easily to Ruby 2.0? That would make the pull request unnecessary, as the default encoding changes from ascii to UTF8, according to this: http://jekyllrb.com/docs/configuration/

@morty
Copy link
Contributor Author

morty commented Aug 4, 2014

Yes, it is easy now to use Ruby > 1.9, especially with the abstraction provided by the RVM alias (so would not require a code change). However it doesn't seem to fix the issue despite what the docs say.

Your question has made me me dig deeper and it seems that it is down to the language environment variables. On the VMs the LC_ALL is set to en_US which makes it choke on the unicode. When running under apache it can be fixed by adding export LANG='en_GB.UTF-8' to /etc/apache2/envvars.

@rossjones
Copy link
Contributor

If you're running under apache, presumably SetEnv LANG 'en_GB.UTF-8' would also work?

@morty
Copy link
Contributor Author

morty commented Aug 4, 2014

@rossjones no, that doesn't seem to work (see here) by this does 1130052

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants