From: John Muccigrosso <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: backslash-escaped leading space in markdown table treated as a literal backslash
Date: Mon, 5 Feb 2018 12:32:53 -0800 (PST) [thread overview]
Message-ID: <1f5e2447-795b-45d4-991b-ed5a55ea706c@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1487 bytes --]
I think this is a relatively recent regression. `\ ` at the start of a line
normally gets treated as a space:
> pandoc
one
\ two
three
<p>one</p>
<p> two</p>
<p>three</p>
But if it's in a table, it gets preserved now. HTML below:
> pandoc
one | one
----|---
two | two
\ | three
<table>
<thead>
<tr class="header">
<th>one</th>
<th>one</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>two</td>
<td>two</td>
</tr>
<tr class="even">
<td>\</td>
<td>three</td>
</tr>
</tbody>
</table>
Native output looks like this:
[Table [] [AlignDefault,AlignDefault] [0.0,0.0]
[[Plain [Str "one"]]
,[Plain [Str "one"]]]
[[[Plain [Str "two"]]
,[Plain [Str "two"]]]
,[[Plain [Str "\\"]]
,[Plain [Str "three"]]]]]
Versus this for the non-table version:
[Para [Str "one"]
,Para [Str "\160two"]
,Para [Str "three"]]
This has only started recently. I noticed it today in a document I last
processed in October 2017.
--
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/1f5e2447-795b-45d4-991b-ed5a55ea706c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 10847 bytes --]
next reply other threads:[~2018-02-05 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:32 John Muccigrosso [this message]
[not found] ` <1f5e2447-795b-45d4-991b-ed5a55ea706c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-02-07 16:52 ` John MacFarlane
[not found] ` <20180207165257.GH88252-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-02-07 21:37 ` John Muccigrosso
[not found] ` <f1c851a4-d1fd-4d2e-a881-d7ad76eb05d6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-02-09 23:26 ` John Muccigrosso
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=1f5e2447-795b-45d4-991b-ed5a55ea706c@googlegroups.com \
--to=jmuccigr-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).