ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Improving pandoc's ConTeXt output
Date: Sun, 5 Jun 2022 12:01:54 +0200	[thread overview]
Message-ID: <0c8a8674-b405-4922-8fb3-2c277111a5ce@xs4all.nl> (raw)
In-Reply-To: <87o7z7pnrm.fsf@zeitkraut.de>

On 6/5/2022 9:07 AM, Albert Krewinkel via ntg-context wrote:
> Hi all,
> 
> I'm currently trying to improve the ConTeXt output generated by pandoc,
> the document convert. There are two questions that we haven't decided
> on, and I'd be grateful to receive some feedback from ConTeXt experts on
> these issues:
> 
> 1. As far as I understand, the `\section` syntax currently produced by
>     pandoc should be considered mkii legacy syntax. We're likely going to
>     switch to the modern `\startsection`/`\stopsection` syntax instead.
>     Are there any concerns about retiring the old syntax?
>     (Side note: pandoc already produces the new syntax, but only when
>     called with `--section-divs`.)

We keep compatibility as much as possible although there are of course 
exceptions (like: we don't need font encodings in mkiv and we hav 
eopentype fonts there). So it si quit elikely that these commands will 
stay forever.

> 2. Similarly, I'd like to start wrapping paragraphs with
>     `\startparagraph`/`\stopparagraph`. It is important for me to get
>     properly tagged PDF, but this would also make the output more
>     verbose. Is that something that you would find bothering, or do you
>     see adding the extra environment by default as an acceptable
>     practice?

I assume not that many users see (or manipulate) the output so it is 
harmless.

> Of course, I'd also be happy to get other suggestions on how to improve
> pandoc's ConTeXt support.
> 
> Thanks in advance,
> 
> Albert
> 
> 


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2022-06-05 10:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  7:07 Albert Krewinkel via ntg-context
2022-06-05  8:20 ` juh via ntg-context
2022-06-05  9:39   ` Denis Maier via ntg-context
2022-06-05 14:15   ` Albert Krewinkel via ntg-context
2022-06-05 16:38     ` juh+ntg-context--- via ntg-context
2022-06-05 23:52       ` Thangalin via ntg-context
2022-06-06  5:21         ` Problem with SVG an conversion mp (was: Improving pandoc's ConTeXt output) Jan U. Hasecke via ntg-context
2022-06-06  5:51         ` Improving pandoc's ConTeXt output juh+ntg-context--- via ntg-context
2022-06-05  9:46 ` Denis Maier via ntg-context
2022-06-05 10:01 ` Hans Hagen via ntg-context [this message]
2022-06-05 11:08   ` Wolfgang Schuster via ntg-context
2022-06-05 14:30     ` Albert Krewinkel via ntg-context
2022-06-06 20:47       ` Henning Hraban Ramm via ntg-context
2022-06-08 13:43 ` Albert Krewinkel via ntg-context

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=0c8a8674-b405-4922-8fb3-2c277111a5ce@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.nl \
    /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).