From: Salim B <salim.brueggemann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to type arrow?
Date: Thu, 28 Sep 2017 11:10:01 -0700 (PDT) [thread overview]
Message-ID: <c749a968-234b-4bd9-97b1-2d0ffeafd4aa@googlegroups.com> (raw)
In-Reply-To: <b27a3f27-81a8-444d-abe4-4b2114a5f220-QDc/DHGF8irHdqrNY7FC6GB/v6IoIuQBVpNB7YpNyf8@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]
Just wanted to note that there's a Pandoc filter (written in Perl) that
converts ASCII arrows to Latex arrows:
https://github.com/nichtich/pandoc-filter-arrows
I've tested it quickly and it seems to work as expected. And even doesn't
interpret/break (multiline) HTML comments (<!-- -->)!
Am Montag, 9. April 2012 23:17:29 UTC+2 schrieb Peng Yu:
>
> Hi,
>
> There is a few ways for typing arrows (left, right). Does anybody know
> the most convenient way?
>
> Regards,
> Peng
--
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/c749a968-234b-4bd9-97b1-2d0ffeafd4aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 416503 bytes --]
prev parent reply other threads:[~2017-09-28 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 21:17 Peng Yu
[not found] ` <b27a3f27-81a8-444d-abe4-4b2114a5f220-QDc/DHGF8irHdqrNY7FC6GB/v6IoIuQBVpNB7YpNyf8@public.gmane.org>
2012-04-10 2:42 ` John Gabriele
[not found] ` <CAO9PwMXzrSWG_M-caWGJy3p0-1GgBPfZMOVhq0qkFKiuvuxZZg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 5:10 ` Peng Yu
[not found] ` <CABrM6wnnrAe7HzvquoLRYKDeiUREaCYgpbLWsPMVd1shkmwmnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 5:26 ` John Gabriele
2012-04-10 5:34 ` Dirk Laurie
[not found] ` <CABcj=t=CcDD_MhQcXrNRDSik1rBi2FCkbPVNzXNC1OhykCKCMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 5:43 ` HansBKK
2012-04-10 5:50 ` Peng Yu
[not found] ` <CABrM6wnACvawOz95WxT5hZr6yxJxQrT4tEX9Qs83+wNW1hiQoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 6:03 ` Peter Wang
[not found] ` <20120410160320.GG8657-j5sBwglC4Qx82hYKe6nXyg@public.gmane.org>
2012-04-10 20:04 ` John MacFarlane
2012-04-10 6:39 ` Werner LEMBERG
2017-09-28 18:10 ` Salim B [this message]
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=c749a968-234b-4bd9-97b1-2d0ffeafd4aa@googlegroups.com \
--to=salim.brueggemann-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).