public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Vít Novotný" <witiko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Plain TeX writer
Date: Wed, 26 Oct 2022 13:09:33 -0700 (PDT)	[thread overview]
Message-ID: <24c01860-2f35-4ff0-9d31-63d10f764f79n@googlegroups.com> (raw)
In-Reply-To: <84C142C7-20EF-411E-AF94-D0AA008FA9DA-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


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


>
> What would you think about replacing \pandocSpace with a regular space 
> character? IT would make the output a lot more readable. Similarly, 
> SoftBreak could be a regular newline character.
>

In drehak/pandoc-to-markdown#20 
<https://github.com/drehak/pandoc-to-markdown/pull/20> and #21 
<https://github.com/drehak/pandoc-to-markdown/pull/21>, we have replaced 
*\pandocSpace* and *\pandocSoftBreak* with ␣ and *⤶*, respectively. Running 
the code from the original post will now produce the following output:


*$ cat example.tex*
*\pandocDocumentBegin*


*Under his pillow P’raps found\pandocLineBreak\pandocStrikeout{A cake that 
weighed a half a pound.}\pandocLineBreakA plenty of space to roll 
around\pandocDocumentEnd*

This is definitely easier on the eye than the original.

-- 
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/24c01860-2f35-4ff0-9d31-63d10f764f79n%40googlegroups.com.

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

  parent reply	other threads:[~2022-10-26 20:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 13:59 Vít Novotný
     [not found] ` <51539828-c876-437b-bb1e-a5efcf752762n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-19 15:43   ` John MacFarlane
     [not found]     ` <84C142C7-20EF-411E-AF94-D0AA008FA9DA-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-19 16:21       ` Vít Novotný
     [not found]         ` <5e9dfe75-ea0e-4287-a6a0-47842700f292n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-20  8:05           ` Bastien DUMONT
2022-10-20  9:13             ` Vít Novotný
     [not found]               ` <a7d769e7-083c-4cb9-a9a2-b5a21b62c8f0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-20  9:53                 ` Bastien DUMONT
2022-10-20 10:32                   ` Vít Novotný
     [not found]                     ` <782726a4-9890-4396-9696-4f5a349f9885n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-20 10:43                       ` Bastien DUMONT
2022-10-26 20:09       ` Vít Novotný [this message]
     [not found]         ` <24c01860-2f35-4ff0-9d31-63d10f764f79n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-27  0:24           ` John MacFarlane
     [not found]             ` <1EC34FB9-2344-40AC-91CD-22B3D9069EE6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-27  7:07               ` Bastien DUMONT
2022-10-27 17:09                 ` John MacFarlane
     [not found]                   ` <B180C2FD-5AD9-47F2-8E5D-8133CCD8CE00-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-02 14:17                     ` Vít Novotný
     [not found]                       ` <9dfc8b26-3fda-4882-93b7-06d44671ef7fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-02 14:23                         ` 'William Lupton' via pandoc-discuss
     [not found]                           ` <CAEe_xxiYD8Y5KJVB7WiKOo5xHbFWPq010rMXJEYsu_XNd-hX4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-02 14:35                             ` Vít Novotný

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=24c01860-2f35-4ff0-9d31-63d10f764f79n@googlegroups.com \
    --to=witiko-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).