From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: Re: ConTeXt as a service
Date: Fri, 22 Nov 2019 16:45:21 +0100 [thread overview]
Message-ID: <169e486f-d8d7-6ec1-0250-031ae2f9d15d@mailbox.org> (raw)
In-Reply-To: <AA15D2C2-D55C-4C39-A271-9B3C681E9A90@fiee.net>
Am 22.11.19 um 10:05 schrieb Henning Hraban Ramm:
> Am 2019-11-22 um 09:46 schrieb Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
>>
>> On Fri, 22 Nov 2019 at 08:51, Jan U. Hasecke wrote:
>>>
>>> I am very interested in running ConTeXt as a service, too. I am still
>>> nurturing the idea of a publishing cooperative for self publishers with
>>> a Markdown --> Pandoc --> ConTeXt workflow with a nice web frontend. I
>>> hope to make it to the next ConTeXt meeting to discuss it.
>>
>> If you want to start from a simple markup language, at least go for
>> asciidoc or restructured text.
>> Markdown is a mess for anything but very very very trivial structure,
>> and very very soon you basically end up with "basically ugly html with
>> some embeded plain text every now and then".
>>
>> There is some proof-of-concept test document which goes via the
>> asciidoc --[asciidoctor]--> docbook (xml) --[context]--> pdf
>> path (but it needs more work to be fully useful).
>
> Wouldn’t it make sense to go (X)HTML->ConTeXt?
This is what I am currently doing locally with Pablos
from-pandoc-to-context workflow.
juh
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-22 15:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 16:07 Denis Maier
2019-11-20 16:43 ` Hans Hagen
2019-11-20 17:10 ` Henning Hraban Ramm
2019-11-20 18:50 ` Hans Hagen
2019-11-22 7:43 ` Jan U. Hasecke
2019-11-22 8:46 ` Mojca Miklavec
2019-11-22 9:05 ` Henning Hraban Ramm
2019-11-22 15:45 ` Jan U. Hasecke [this message]
2019-11-22 23:44 ` denis.maier.lists
2019-11-23 7:12 ` Mojca Miklavec
2019-11-23 12:02 ` Henning Hraban Ramm
2019-11-23 12:18 ` luigi scarso
2019-11-23 13:18 ` Henning Hraban Ramm
2019-11-23 14:03 ` mf
2019-11-24 11:00 ` Hans Hagen
2019-11-23 14:14 ` Mojca Miklavec
2019-11-23 15:39 ` Henning Hraban Ramm
2019-11-23 15:50 ` Mojca Miklavec
2019-11-23 16:03 ` Henning Hraban Ramm
2019-11-24 10:56 ` Hans Hagen
2019-11-23 14:24 ` mf
2019-11-23 15:39 ` mf
2019-11-24 10:51 ` Hans Hagen
2019-11-21 2:00 Brian Ballsun-Stanton
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=169e486f-d8d7-6ec1-0250-031ae2f9d15d@mailbox.org \
--to=juh+ntg-context@mailbox.org \
--cc=ntg-context@ntg.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).