From: luigi scarso via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: luigi scarso <luigi.scarso@gmail.com>
Subject: Re: ConTeXt features in pandoc 3
Date: Mon, 23 Jan 2023 09:24:09 +0100 [thread overview]
Message-ID: <CAG5iGsDPtwPOrxsLULfZ8ZzA_DTEjFos0-BYsH8FJWsi_csy=g@mail.gmail.com> (raw)
In-Reply-To: <Y841xpl7mVv3NFSg@odysseus>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
On Mon, 23 Jan 2023 at 08:30, juh via ntg-context <ntg-context@ntg.nl>
wrote:
>
> 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.
>
It would be very nice to have a paper / wiki / whatever ... about
your workflow Markdown --> Pandoc --> ConTeXt using Org-Mode.
In these cases, having "a working workflow" to start with is much better
than nothing.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1820 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 8:24 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
2023-01-23 8:24 ` luigi scarso via ntg-context [this message]
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='CAG5iGsDPtwPOrxsLULfZ8ZzA_DTEjFos0-BYsH8FJWsi_csy=g@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=luigi.scarso@gmail.com \
/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).