You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I write `Pandoc` inline within a markdown input file, it displays with a different font as Pandoc which is fine. However, that seems to be done by simply changing the font to Courier New for an ODT output file.
The same input used to create a DOCX file attaches the Verbatim Char character style to the verbatim inline text, which I can control by adjusting this style in my custom-reference.docx file I add to the command line options.
Is there a way to get the ODT output to behave the same. That is, add a character style to inline verbatim text instead of simply changing the font? I could then control this style in a custom-reference.odt file.
The text was updated successfully, but these errors were encountered:
Also the font-size of verbatim is fixed to 10pt. This gives arkward results when used inside a header or if used inline inside text blocks using a different font-size.
Yes, the opendocument writer is currently fairly primitive. I didn't write it, and I don't understand the details of the format well enough to change it. But it would be nice for someone to take this on, replacing all the auto-generated styles with real styles.
If I write `Pandoc` inline within a markdown input file, it displays with a different font as
Pandoc
which is fine. However, that seems to be done by simply changing the font to Courier New for an ODT output file.The same input used to create a DOCX file attaches the Verbatim Char character style to the verbatim inline text, which I can control by adjusting this style in my
custom-reference.docx
file I add to the command line options.Is there a way to get the ODT output to behave the same. That is, add a character style to inline verbatim text instead of simply changing the font? I could then control this style in a
custom-reference.odt
file.The text was updated successfully, but these errors were encountered: