Replies: 5 comments 4 replies
-
|
Using this version of pandoc: |
Beta Was this translation helpful? Give feedback.
-
|
I've tried a lot of variations and I can't get it to pass anything to the and here's what I think should work, using the documentation as a guide: Ignore the backslashes before the triple backquotes. |
Beta Was this translation helpful? Give feedback.
-
|
What you want is |
Beta Was this translation helpful? Give feedback.
-
|
Or just |
Beta Was this translation helpful? Give feedback.
-
|
I decided to write a script to add the proper HTML to the output file. Not optimal, but a simple fix. I realize this whole issue was created by Google and the developers might not want to add a "fix" for this to pandoc. That's fine, I would understand. I do think the fact that I can't add things to the |
Beta Was this translation helpful? Give feedback.
-
|
Your version of Pandoc is very old. Using the latest version, the method tried in your first message works.
|
Beta Was this translation helpful? Give feedback.
-
|
The issue here is that the |
Beta Was this translation helpful? Give feedback.
-
|
The issue is #3139 |
Beta Was this translation helpful? Give feedback.
-
|
It is pretty easy to modify your local (possibly local default) templates for any sets of includes which don’t interact with after and then just before (See Templates in the Pandoc manual!) and then in your metadata: before-header:
latex:
- |
```{=latex}
\usepackage{mypackage}
\include{myinclude.ltx}
```
html:
- |
```{=html}
<link rel="stylesheet" href="mystyle.css" />
```
after-header:
html:
- |
```{=html}
<style>
.red { color: red }
</style>
```Note that you still have to wrap the actual markup in raw blocks to avoid Markdown escaping! Or you could put it in a defaults file like this to avoid that: (See Defaults files in the Pandoc manual!) variables:
before-header:
latex:
- |
\usepackage{mypackage}
\include{myinclude.ltx}
html:
- |
<link rel="stylesheet" href="mystyle.css" />
after-header:
html:
- |
<style>
.red { color: red }
</style>You can of course also have includes:
latex:
header:
before:
# list of markup blocks
after:
# list of markup blocks
body:
before:
# list of markup blocks
after:
# list of markup blocks
html:
# You get the ideaand then in your latex template etc. Of course in your html template you could have $for(link-css)$
<link rel="stylesheet" href="$link-css$" />
$endfor$
$if(css-style)$
<style>
$for(css-style)$
$css-style$
$endfor$
</style>
$endif$and then in your defaults file variables:
link-css:
- mystyle.css
css-style:
- |
.red { color: red }In other words you can include anything from metadata and variables you like however you like in your templates, and as long as you use other names than those variables which pandoc associates with its commandline options your custom fields will be totally independent. In my custom latex template I for example have: $for(ltx-pkg)$
$if(ltx-pkg.opts)$
\usepackage[$--
$for(ltx-pkg.opts)$
$ltx-pkg.opts$$sep$,
$endfor$
]{$ltx-pkg.name$}
$else$
\usepackage{$if(ltx-pkg.name)$$ltx-pkg.name$$else$$ltx-pkg$$endif$}
$endif$
$endfor$which with this in a defaults file variables:
ltx-pkg:
- foopack
- name: ulem
opts: normalem
- name: mypack
opts:
- tic=tac
- toc
- tuc
- name: barpackgives this in my latex header \usepackage{foopack}
\usepackage[
normalem]{ulem}
\usepackage[
tic=tac,
toc,
tuc]{mypack}
\usepackage{barpack}Now I guess someone ought to make a PR for adding all those |
Beta Was this translation helpful? Give feedback.
-
We generate our documentation with pandoc and Google is complaining about the fact we have no canonical version set, since we have multiple versions of the documentation and they want to know which one is canonical. This is done via
The source is in Markdown and I tried adding this to the
.mdfiles but it did not work (the code doesn't appear in the output.htmlfile):Ideas? IMO, it would be a very nice feature to add to pandoc to add this to
<head>...</head>automatically.Beta Was this translation helpful? Give feedback.
All reactions