From: juh via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: juh <juh+ntg-context@mailbox.org>
Subject: Re: ConTeXt features in pandoc 3
Date: Mon, 23 Jan 2023 08:22:46 +0100 [thread overview]
Message-ID: <Y841xpl7mVv3NFSg@odysseus> (raw)
In-Reply-To: <20230122161109.05e8e4e1@atmarama.ddns.net>
[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]
Am Sun, Jan 22, 2023 at 04:11:09PM +0100 schrieb Saša Janiška via ntg-context:
> I'll probably start to work on a book soon and would like to typeset it using
> ConTeXt, but wonder which markup to use as a source in a Markdown (via Pandoc)
> --> ConTeXt or possibly org-mode (via Pandoc) --> ConTeXt?
>
> Anyone has some serious experience with org-mode (via ox-context) --> ConTeXt?
At work at my cooperative Hostsharing eG we use the way Markdown -->
Pandoc --> ConTeXt and we are quite happy with the results. Sadly I
don't have time to document it in full up to now.
For my own writing I was using Markdown --> Pandoc --> ConTeXt for quite
a while and was happy with it, too. Recently I switched to Org-Mode as I
started to use org-roam to organize my Zettelkasten and want to make use
of the org-mode TODO workflow states to organize the writing process. I
use org-pandoc to export from org-mode/emacs to context. I can also use
ox-context but I have difficulties to customize it to my needs.
The main problem is that both org-pandoc and ox-context are developed by
very few people. My lisp knowledge is very limited so I have to stick
with what is there.
Having a solid pipe from the first ideas to the print pdf would be nice.
For now I would say that the exports from org-mode are the weak element
in the chain. But if they fail I can export to Markdown and do the last
steps via Markdown --> Pandoc.
That said I have to confess that I do more sophisticated layout things
like flyers in pure ConTeXt as it is much faster.
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: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-23 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 21:00 Albert Krewinkel via ntg-context
2023-01-20 23:48 ` Pawel Urbanski via ntg-context
2023-01-22 15:11 ` Saša Janiška via ntg-context
2023-01-23 7:22 ` juh via ntg-context [this message]
2023-01-23 8:24 ` luigi scarso via ntg-context
2023-01-24 6:22 ` Saša Janiška 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=Y841xpl7mVv3NFSg@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).