From: K4zuki <k.yamamoto.08136891-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Tex RawInline and following alphanumeric span get merged (2.19+)
Date: Sat, 5 Aug 2023 11:47:22 -0700 (PDT) [thread overview]
Message-ID: <cf53af8c-b1be-485f-9ef7-c1554cf4611an@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1132 bytes --]
Hello,
When trying to pick a tex RawInline, some particular case has a problem.
Converting following markdown code to native is not what I expect
#### Input
```markdown
\linebreak [0]{custom-style="NormalTok"}
```
#### Expected output
```
[ Para
[ RawInline (Format "tex") "\\linebreak"
, Space
, Span
( "" , [] , [ ( "custom-style" , "NormalTok" ) ] )
[ Str "0" ]
]
]
```
#### Actual output
```
[ RawBlock
(Format "tex") "\\linebreak [0]{custom-style=\"NormalTok\"}"
]
```
#### Confirmed pandoc versions
- 2.19.2
- 3.1.1
Could you guys advise if this is a bug or expected behavior, and what could
be a workaround? So far I found `\linebreak{}` works.
Thanks && Regards,
Kazuki
--
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/cf53af8c-b1be-485f-9ef7-c1554cf4611an%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1801 bytes --]
next reply other threads:[~2023-08-05 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 18:47 K4zuki [this message]
[not found] ` <cf53af8c-b1be-485f-9ef7-c1554cf4611an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-05 22:33 ` Bastien DUMONT
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=cf53af8c-b1be-485f-9ef7-c1554cf4611an@googlegroups.com \
--to=k.yamamoto.08136891-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).