Update environment and documentation #81
Conversation
Pandoc upgraded to v2.0.0.1
dhimmel
force-pushed
the
update-env-2017-10-31
branch
from
24be208 to
46577a2
Compare
WeasyPrint was not renderring MathJax, so use --webtex to convert equations to SVGs for PDF output. See Kozea/WeasyPrint#59
This build is based on ec186c2. This commit was created by the following Travis CI build and job: https://travis-ci.org/greenelab/manubot-rootstock/builds/295841617 https://travis-ci.org/greenelab/manubot-rootstock/jobs/295841618 [ci skip] The full commit message that triggered this build is copied below: Update environment and documentation (#81) Pandoc upgraded to v2.0.0.1 Swap anaconda packages to conda-forge Update build.sh for pandoc 2.0 WeasyPrint was not renderring MathJax, so use --webtex to convert equations to SVGs for PDF output. See Kozea/WeasyPrint#59
This build is based on ec186c2. This commit was created by the following Travis CI build and job: https://travis-ci.org/greenelab/manubot-rootstock/builds/295841617 https://travis-ci.org/greenelab/manubot-rootstock/jobs/295841618 [ci skip] The full commit message that triggered this build is copied below: Update environment and documentation (#81) Pandoc upgraded to v2.0.0.1 Swap anaconda packages to conda-forge Update build.sh for pandoc 2.0 WeasyPrint was not renderring MathJax, so use --webtex to convert equations to SVGs for PDF output. See Kozea/WeasyPrint#59
| @@ -120,7 +120,7 @@ For guidance on what CSL JSON should be like for different document types, refer | |||
| ## Manuscript metadata | |||
|
|
|||
| [`content/metadata.yaml`](content/metadata.yaml) contains manuscript metadata that gets passed through to Pandoc, via a [`yaml_metadata_block`](http://pandoc.org/MANUAL.html#extension-yaml_metadata_block). | |||
| `metadata.yaml` should contain the manuscript `title`, `authors` list, and `keywords`. | |||
| `metadata.yaml` should contain the manuscript `title`, `authors` list, `keywords`, and language (`lang`). | |||
There was a problem hiding this comment.
@dhimmel can we link to a list of valid language codes?
There was a problem hiding this comment.
From Pandoc docs:
lang: identifies the main language of the document, using a code according to BCP 47 (e.g.enoren-GB). For some output formats, pandoc will convert it to an appropriate format stored in the additional variablesbabel-lang,polyglossia-lang(LaTeX) andcontext-lang(ConTeXt).
I will look for a BCP 47 list of language codes.
There was a problem hiding this comment.
BCP 47 codes can combine a language and region. Language codes are defined here. Region codes are here.
These BCP 47 codes can get quite complex it seems as they can have the following parts:
language-extlang-script-region-variant-extension-privateuse
There's an unofficial validator at http://schneegans.de/lv/ that may be helpful. Wonder how complicated we want to make these docs!
There was a problem hiding this comment.
Great info. Linking to one or two of those resources could help users without adding much more complexity to these manubot docs.
As a general Python question, why do you prefer conda-forge over anaconda? Does it provide more flexibility or more frequent updates because it is community-driven? |
|
conda-forge is an open system, whereas the anaconda recipes to build packages are not public (see comment here). In the past, anaconda had greater package coverage, but lately I think conda-forge now has better coverage and generally is updated with new versions more quickly. In addition, if conda-forge is outdated, you can update it yourself, like I did in conda-forge/pandoc-feedstock#19. Previously, we were only using conda-forge for packages that weren't available in anaconda. However, once I experienced an error from using an R binary from the anaconda R channel and an R package from conda-forge. So I think it's ideal to rely on a single channel for all packages if possible. Now conda-forge seems to be mature enough to support this. |
Thanks, that's a very helpful explanation. I now recall a blog post that described what you noted about mixing channels. On a related note, the Anaconda 5.0 release notes state
|
This build is based on 46824e6. This commit was created by the following Travis CI build and job: https://travis-ci.org/greenelab/manubot-rootstock/builds/296253421 https://travis-ci.org/greenelab/manubot-rootstock/jobs/296253422 [ci skip] The full commit message that triggered this build is copied below: USAGE.md: link to language tag documentation (#83) #81 (comment)
This build is based on 46824e6. This commit was created by the following Travis CI build and job: https://travis-ci.org/greenelab/manubot-rootstock/builds/296253421 https://travis-ci.org/greenelab/manubot-rootstock/jobs/296253422 [ci skip] The full commit message that triggered this build is copied below: USAGE.md: link to language tag documentation (#83) #81 (comment)
Pandoc upgraded to v2.0.0.1.
Swap anaconda packages to conda-forge.