From: "Vít Novotný" <witiko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Plain TeX writer
Date: Thu, 20 Oct 2022 02:13:15 -0700 (PDT) [thread overview]
Message-ID: <a7d769e7-083c-4cb9-a9a2-b5a21b62c8f0n@googlegroups.com> (raw)
In-Reply-To: <Y1EBU0Ch0HHr2geB@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1921 bytes --]
Dne čtvrtek 20. října 2022 v 10:06:23 UTC+2 uživatel Bastien Dumont napsal:
> I don't understand either the rationale for \pandocSpace and
> \pandocLinebreak. Since Markdown and TeX agree on handling simple line
> breaks and repeated spaces like single spaces, in what cases would it be
> useful?
I was going to give an example of a Word document with the text
*Hello␣␣␣world!* and show that it would produce the output *Hello
\pandocSpace{}\pandocSpace{}\pandocSpace{}world!*, which would allow us to
preserve the repeated spaces. Howover, running *pandoc -i example.docx -t
pandoc-to-markdown.lua* produces *Hello\pandocSpace{}world!* as the output.
This indicates that not only Markdown and TeX fold repeated spaces, but
Pandoc's AST in general does. In that case, it seems reasonable to replace
*\pandocSpace{}* with *␣* and *\pandocLineBreak{}* with *⤶* in the TeX
output as John also suggested.
Thanks to the package xkeyval, the key-value argument could be handled
> quite easily in all formats that include Plain TeX.
>
The xkeyval package is one option. I am partial to the expl3 programming
language <https://www.ctan.org/pkg/l3kernel> from the LaTeX3 project, which
provides many programming extensions to TeX, including key--value
interfaces (see the l3keys module in the LaTeX3 Interface Documentation
<http://mirrors.ctan.org/macros/latex/contrib/l3kernel/interface3.pdf>).
However, some would call the syntax of expl3 arcane.
--
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/a7d769e7-083c-4cb9-a9a2-b5a21b62c8f0n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2693 bytes --]
next prev parent reply other threads:[~2022-10-20 9:13 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ý [this message]
[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ý
[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=a7d769e7-083c-4cb9-a9a2-b5a21b62c8f0n@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).