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
I'm compiling a PDF using xelatex, and I'd like smart quotes to work (as per https://pandoc.org/MANUAL.html#typography). According to the README, this should be possible using the #+PANDOC_EXTENSIONS: smart option, however I'm not getting the desired result.
I may be misunderstanding how it works though. As far as I've been able to determine, the smart extension should be passed to the input format in Pandoc, eg --from org+smart from the command line does work. I tried passing different values to #+PANDOC_EXTENSIONS:, but I haven't been able to find one that works.
I did manage to get it to work using #+PANDOC_OPTIONS: from:org+smart, however that required me to add "from" to org-pandoc-valid-options.
Is this a bug? Is this a documentation issue? Or am I just doing something wrong?
The text was updated successfully, but these errors were encountered:
While converting from org to docx, the "smart" extension is supposed to passed to pandoc command as -f org+smart as -t docx+smart is not supported. Whereas in the code, we are not appending the extensions to -f org parameter.
Hello!
I'm compiling a PDF using xelatex, and I'd like smart quotes to work (as per https://pandoc.org/MANUAL.html#typography). According to the README, this should be possible using the
#+PANDOC_EXTENSIONS: smart
option, however I'm not getting the desired result.I may be misunderstanding how it works though. As far as I've been able to determine, the
smart
extension should be passed to the input format in Pandoc, eg--from org+smart
from the command line does work. I tried passing different values to#+PANDOC_EXTENSIONS:
, but I haven't been able to find one that works.I did manage to get it to work using
#+PANDOC_OPTIONS: from:org+smart
, however that required me to add "from" toorg-pandoc-valid-options
.Is this a bug? Is this a documentation issue? Or am I just doing something wrong?
The text was updated successfully, but these errors were encountered: