public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: matsuoka <kokoro601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Inline math does not render properly
Date: Fri, 24 Nov 2023 17:52:22 -0800 (PST)	[thread overview]
Message-ID: <b2796085-1d5c-41c7-8772-5bedaca11da7n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]

I converted a markdown file like below into html.

[Link](http://example.com)Text $x$

Github renders this properly.


[image: github.png]
However, when converted with pandoc test.md -o test.html --standalone 
--katex -f gfm, inline math does not render properly (Same thing happened 
when it is converted with mathjax). It seems that there should be a space 
just after the link in order for pandoc to parse this file correctly. Is 
this an expected behavior? I have a lot of markdown files that contains a 
pattern like above, so I want inline math to be parsed properly.

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b2796085-1d5c-41c7-8772-5bedaca11da7n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1467 bytes --]

[-- Attachment #2: github.png --]
[-- Type: image/png, Size: 12887 bytes --]

             reply	other threads:[~2023-11-25  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  1:52 matsuoka [this message]
     [not found] ` <b2796085-1d5c-41c7-8772-5bedaca11da7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-05 15:04   ` Julien Dutant

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=b2796085-1d5c-41c7-8772-5bedaca11da7n@googlegroups.com \
    --to=kokoro601-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).