public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Lloyd R. prentice" <lloyd-l7gIAb2iU4jcM+WK4BI3xw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: djot - a new light markup language
Date: Mon, 18 Jul 2022 16:15:09 -0400	[thread overview]
Message-ID: <96DFE84C-B390-4029-95AF-CA6ABC484447@writersglen.com> (raw)

Hi,

Can’t speak up for Jon, but I’m much interested in a markdown variant that meets the needs of book publishers, particularly self-publishers.  The LaTeX markdown package is a good start. But in my naive view it needs a cleaner bridge to the full expressive power of LaTeX—something like the bridge between HTML and CSS.

The basic tags of extended Pandoc markdown go far. But it would be productive to somehow simply mark a block of copy and apply an arbitrary LaTeX package or snippet. This can be done with the LaTeX markdown package at the cost of dropping down into plain TeX which is much harder to learn than CSS and likely far beyond the skill set of most self-publishers.

Perhaps djot holds this potential, but I don’t yet understand it well enough to see how.

All the best,

LRP

Sent from my iPad

> On Jul 18, 2022, at 12:24 PM, Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> wrote:
> Jon, I was wondering if you could speak to how you'd like to see markdown variants progress, especially since you are now behind three of them! 🙂
> 
> - CommonMark: a best attempt at formalizing the ambiguities of legacy markdown; stable (no more features); you recommend new efforts adopt djot or pandoc-markdown.
> - djot: simpler to implement and likely to see easily implementable features.
> - pandoc-markdown: CommonMark with powerful extensions (e.g., bibliography).
> 
> 
> On 22-07-18 12:08, John MacFarlane wrote:
>> If I did include something as standard syntax, I'd be inclined not to make it YAML, which is too complicated, but maybe a YAML subset.
> 
> -- 
> 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/5a12655c-c8a0-e5ab-c173-a4ea9cf8c661%40reagle.org.

-- 
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/96DFE84C-B390-4029-95AF-CA6ABC484447%40writersglen.com.


             reply	other threads:[~2022-07-18 20:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 20:15 Lloyd R. prentice [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=96DFE84C-B390-4029-95AF-CA6ABC484447@writersglen.com \
    --to=lloyd-l7giab2iu4jcm+wk4bi3xw@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).