Johannes Ranke

Please have a look at #476. Personally, I am using this. ```" The following is adapted from issue https://github.com/jalvesaq/Nvim-R/issues/476 function StartRdevel() let g:R_path = '~/svn/R/r-devel/build/bin' call StartR("R-devel") endfunction nmap ,rx...

You can also use ``` :make ```

The translation feature was developed using pelican 3.6.3 and it used to work for me. Sorry for the inconvenience. I just upgraded to pelican 3.7.0 and got the error about...

Obviously `gettext` needs to be installed into the jinja environment using a call to `jinja2.Environment.install_gettext_callables` as documented [here](http://jinja.pocoo.org/docs/dev/extensions/). However, I do not know how to access the environment that is...

@gravyboat Thanks for the heads-up! This translation stuff seems not to be used so much in pelican themes...

For what it's worth, I just downgraded pelican to 3.6.3 (from Debian jessie-backports), went back to the previous configuration using `JINJA_EXTENSIONS` and `pelican-bootstrap3` from current master works with this setting....

It seems to me that this needs to be taken care of in pelican itself, so gettext (and maybe newgettext) can be installed via the pelican config file.

Thanks for having a look. I thought it would need to be `install_gettext_callables`, as mentioned above? But I have not done any tests and have no context either...

Maybe it is just the jinja version that's causing the difference. I can't test right now, but I have a website using i18n, so I hope to be able to...

@avaris and @justinmayer: I see it differently: Removing the setting `JINJA_EXTENSIONS` from the pelican config broke the i18n_subsites plugin.