From: Hannu Kokko <hannu.tapio.kokko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Left braces not coming out correctly - what to do?
Date: Tue, 19 Sep 2017 04:57:21 -0700 (PDT) [thread overview]
Message-ID: <a1fa14a7-7391-4f68-a045-4b43a9388d9f@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1384 bytes --]
Running latest TexShop on the latest MacOS X with latest LaTex and latest
pandoc.
The following pandoc typeset
\documentclass{article}\begin{document}\begingroup\obeylines
\{\}
\endgroup%
\end{document}
Produces
\{}
I would have expected
{}
This is the pandoc parameter/script file
#!/bin/bash
# pandoc takes an input file (usually markdown) and writes an output file (latex, epub, ...)
# There is a shortcut to create pdf from markdown via latex called markdown2pdf.
# See http://johnmacfarlane.net/pandoc/
PATH=$PATH:/Library/TeX/texbin:/usr/texbin:/usr/local/bin
fname_with_ext=$(basename "$1")
fname="${fname_with_ext%.*}.txt"
pandoc "$1" -s -t asciidoc --no-tex-ligatures --wrap=preserve -o $fname
What do I need to change to get both curly braces correct in effect to
produce
{}
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a1fa14a7-7391-4f68-a045-4b43a9388d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 21950 bytes --]
next reply other threads:[~2017-09-19 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 11:57 Hannu Kokko [this message]
[not found] ` <a1fa14a7-7391-4f68-a045-4b43a9388d9f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-19 16:16 ` John MacFarlane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1fa14a7-7391-4f68-a045-4b43a9388d9f@googlegroups.com \
--to=hannu.tapio.kokko-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).