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: djot - a new light markup language
Date: Fri, 15 Jul 2022 23:48:49 +0200	[thread overview]
Message-ID: <CADAJKhB74D6XrZ84mKL6zbeq=PSyKcekh6LQjENTqu9Gx_Mj=w@mail.gmail.com> (raw)
In-Reply-To: <EF9566B8-7F8B-49BD-9FFB-B370750C73BF-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>

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

This is very interesting, especially the way curlies are used to make
opening/closing delimiters explicit and to extend the inventory of possible
delimiters. If I may I would like to suggest adding {|underline|},
{!strikeout!} and {.small caps.}.[^1]

Small caps are somewhat frequent in linguistics (mainly for grammatical
tags in interlinear glosses) so their absence is a problem for me, albeit a
problem which can be worked around with a span with a class.

I actually like the four space rule, but I guess nothing stops me from just
always make sure that a list marker is followed by at least three space
characters. Hopefully this will be easier to live with with indented code
blocks gone!

[^1]: Incidentally this is the same solution as I used in the home grown
lightweight markup which I used before I discovered Pandoc, except there
the curlies were always mandatory. I used a Perl hash mapping punctuation
characters to LaTeX command names and a simple regex substitution
`s/\{([[:punct:]])|[[:punct:]]\}/$1 ? "\\$command{$1}\{" : "}"/eg` except
that `[:punct:]` was the list of actually used characters. Those were the
days! FWIW I differentiated between {_emph_} for emphasis and {/textit/}
for object language.


Den tors 14 juli 2022 23:58John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:

> I've been designing a new light markup syntax, based on the ideas in my
> essay "Beyond Markdown" (https://johnmacfarlane.net/beyond-markdown.html).
> I thought readers of this list might be interested.  The language and its
> rationale are described here:  https://github.com/jgm/djot
>
> The repository also contains a very fast parser written in pure Lua.  A
> pandoc custom reader and custom writer are also provided, so you can
> convert your favorite formats to and from djot.
>
> The syntax is briefly described here:
> https://djot.net/playground/syntax.html
>
> You can play with the implementation here: https://djot.net/playground/
>
> John
>
> --
> 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/EF9566B8-7F8B-49BD-9FFB-B370750C73BF%40berkeley.edu
> .
>

-- 
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/CADAJKhB74D6XrZ84mKL6zbeq%3DPSyKcekh6LQjENTqu9Gx_Mj%3Dw%40mail.gmail.com.

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

  parent reply	other threads:[~2022-07-15 21:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 21:57 John MacFarlane
     [not found] ` <EF9566B8-7F8B-49BD-9FFB-B370750C73BF-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
2022-07-14 22:48   ` T. Kurt Bond
2022-07-14 23:00   ` Leonard Rosenthol
     [not found]     ` <CALu=v3LE+b5xZzTzETK-uJbR64D8O49f6dQ5KGKS_hhzY1q4dQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-15  5:44       ` Lloyd R. prentice
2022-07-15 19:16   ` Albert Krewinkel
2022-07-15 21:48   ` BPJ [this message]
2022-07-18 16:09     ` John MacFarlane
2022-07-18  8:55   ` Philip Hodder
     [not found]     ` <f6b75a75-ca6c-4fbf-a01c-9697646ef445n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-18 16:08       ` John MacFarlane
     [not found]         ` <92CF0240-8135-414E-8E34-4121AC71A9A8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-18 16:24           ` Joseph Reagle
     [not found]             ` <5a12655c-c8a0-e5ab-c173-a4ea9cf8c661-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-07-18 18:09               ` John MacFarlane
2022-07-18 19:54   ` BPJ
     [not found]     ` <CADAJKhAHt-T=1cUqThR=qZQXaBzx0=xzV1vmVNCNhrmSFE+guQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-20  2:45       ` John Gabriele
     [not found]         ` <93545219-f69d-48e6-a730-58aaddacb4dd-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2022-07-25 22:08           ` John MacFarlane
2022-07-18 20:15 Lloyd R. prentice
     [not found] ` <96DFE84C-B390-4029-95AF-CA6ABC484447-l7gIAb2iU4jcM+WK4BI3xw@public.gmane.org>
2022-07-19  6:14   ` 'juh' via pandoc-discuss
2022-07-19 13:56     ` Lloyd R. prentice
     [not found]       ` <13939C0B-E70D-441B-9783-6D0E858EDD2B-l7gIAb2iU4jcM+WK4BI3xw@public.gmane.org>
2022-07-19 14:10         ` Bastien DUMONT
2022-07-20  3:22           ` Lloyd R. prentice

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='CADAJKhB74D6XrZ84mKL6zbeq=PSyKcekh6LQjENTqu9Gx_Mj=w@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).