public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Line breaks (Was: Re: Unsupported extension in Commonmark_x resulting in alternative output)
Date: Thu, 23 Jun 2022 21:11:49 +0200	[thread overview]
Message-ID: <CADAJKhBAz2bzrfvAyLRBT7KBKJOmsdqw-0EnV4G3fkxzBoC2Fw@mail.gmail.com> (raw)
In-Reply-To: <377aa06e-714c-ba4a-5445-dc9d518b95ab-Jdbf3xiKgS8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2392 bytes --]

+1

Den tors 23 juni 2022 15:20Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> skrev:

> On 6/23/22 2:21 AM, John MacFarlane wrote:
> > This is a bit tricky.  escaped_line_breaks isn't really an
> > extension for commonmark, because it is part of the core spec.
> > The writer uses two spaces instead; both are supported according
> > to the spec, and the writer has to make a choice.
>
> As an aside, that particular choice always is a bit touchy to me - while
> it *looks* nice, many text editors (including BBEdit, my preferred) will
> automatically strip whitespace at the end of a line.  Many users won't
> realize it's there in the first place after all, and extra whitespace
> can make handling text documents awkward using automated tools.  (And,
> in case it ever matters, it can bloat filesizes.)
>
> So relying on whitespace at the end of a line for required behavior is
> uncertain at best, in my experience - and this is one thing where I
> often have to go back in and manually edit Markdown files after I've
> formatted them with Pandoc.
>
> Daniel T. Staal
>
> --
> ---------------------------------------------------------------
> This email copyright the author.  Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes.  This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---------------------------------------------------------------
>
> --
> 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/377aa06e-714c-ba4a-5445-dc9d518b95ab%40usa.net
> .
>

-- 
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/CADAJKhBAz2bzrfvAyLRBT7KBKJOmsdqw-0EnV4G3fkxzBoC2Fw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 3363 bytes --]

  parent reply	other threads:[~2022-06-23 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 19:23 Unsupported extension in Commonmark_x resulting in alternative output Thomas Byskov Dalgaard
     [not found] ` <7F040099-8F18-41C2-BB05-0A4658311704-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
2022-06-23  6:21   ` John MacFarlane
     [not found]     ` <m2pmizrjc5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-23 13:19       ` Line breaks (Was: Re: Unsupported extension in Commonmark_x resulting in alternative output) Daniel Staal
     [not found]         ` <377aa06e-714c-ba4a-5445-dc9d518b95ab-Jdbf3xiKgS8@public.gmane.org>
2022-06-23 19:11           ` BPJ [this message]
2022-06-23 20:17           ` John MacFarlane
     [not found]             ` <m25ykrqgmk.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-23 20:51               ` Thomas Byskov Dalgaard
2022-06-24 14:06               ` Daniel Staal
2022-06-23 14:13       ` Unsupported extension in Commonmark_x resulting in alternative output Albert Krewinkel

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=CADAJKhBAz2bzrfvAyLRBT7KBKJOmsdqw-0EnV4G3fkxzBoC2Fw@mail.gmail.com \
    --to=melroch-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).