public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Julien Dutant <julien.dutant-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Inline math does not render properly
Date: Tue, 5 Dec 2023 07:04:57 -0800 (PST)	[thread overview]
Message-ID: <62bf5eb8-f817-4de0-b0a4-6bc739794d17n@googlegroups.com> (raw)
In-Reply-To: <b2796085-1d5c-41c7-8772-5bedaca11da7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

This seems to work fine:

pandoc --mathjax
[Link](example.com)Text $x$

Output:

<p><a href="example.com">Link</a>Text <span
class="math inline">\(x\)</span></p>

Perhaps clarify what output you expect.
On Saturday, November 25, 2023 at 12:52:22 PM UTC+11 matsuoka wrote:

> 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/62bf5eb8-f817-4de0-b0a4-6bc739794d17n%40googlegroups.com.

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

      parent reply	other threads:[~2023-12-05 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  1:52 matsuoka
     [not found] ` <b2796085-1d5c-41c7-8772-5bedaca11da7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-05 15:04   ` Julien Dutant [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=62bf5eb8-f817-4de0-b0a4-6bc739794d17n@googlegroups.com \
    --to=julien.dutant-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).