ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: juh via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: juh <juh+ntg-context@mailbox.org>
Subject: Re: Improving pandoc's ConTeXt output
Date: Sun, 5 Jun 2022 10:20:29 +0200	[thread overview]
Message-ID: <YpxnTZ3tz9Pjb68Q@odysseus> (raw)
In-Reply-To: <87o7z7pnrm.fsf@zeitkraut.de>


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

Dear Albert,

great to hear that, as my cooperative uses pandoc to produce print stuff
with ConTeXt, we are always happy, when there are improvements.

Am Sun, Jun 05, 2022 at 09:07:37AM +0200 schrieb Albert Krewinkel via ntg-context:
> 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?

A similiary question came up in the org-mode mailinglist some weeks ago.

(Background: Org-mode is a markup used with Emacs to make single source
publishing possible)

Someone who maintains an export programme for ConTeXt uses 
sectionlevels.

You get the incremental subsections and subsubsection like this.

\startsectionlevel
  \startsectionlevel
    \startsectionlevel
    \stopsectionlevel
  \stopsectionlevel
\stopsectionlevel

This makes it possible to ignore the part-chapter-section naming
convention and be more flexible. You can leave it to the style files to
decide which level is a part, chapter, section etc...

As I do not use this in production – only playing around with emacs and
org-mode – I cannot say if this is a good way.

Have you considered sectionlevel?
What is your opinion?

juh

-- 
Autoren-Homepage: ......... http://literatur.hasecke.com
Satiren & Essays: ......... http://www.sudelbuch.de
Privater Blog: ............ http://www.hasecke.eu
Netzliteratur-Projekt: .... http://www.generationenprojekt.de



[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2022-06-05  8:20 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 [this message]
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
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=YpxnTZ3tz9Pjb68Q@odysseus \
    --to=ntg-context@ntg.nl \
    --cc=juh+ntg-context@mailbox.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).