From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: other markup to ConTeXt (was: simplefonts or Typecripts)
Date: Fri, 13 Aug 2010 22:56:00 +0000 [thread overview]
Message-ID: <AANLkTi=nWNONKgueYLb4CS7o9jR7+r1K3+w-v3+=Sg4S@mail.gmail.com> (raw)
In-Reply-To: <B8D1BE27-C7CB-4FEA-9CCA-AFB17F794FFD@fiee.net>
This is very similar to a project in which I am planning to engage in
the near future. Output to both HTML and PDF utilizing a simple markup
seems to be a "killer feature" that at least some of us are looking
for. Cross-media publishing, however, is never painless. It's like a
Holy Grail.
Pandoc makes me want to either learn Haskell or implement my own
markup with a focus towards multiple output formats and typesetting in
general (most markups seem to be focused on developer workflows).
Anyway, a fruitful space for ConTeXt, thanks to its strive for configurability.
On Fri, Aug 13, 2010 at 8:35 PM, Henning Hraban Ramm <hraban@fiee.net> wrote:
> Am 2010-08-13 um 21:11 schrieb Gour D.:
>>
>> For now, it can be enough considering that atm we'll mostly write
>> markdown/reST and convert to ConTeXt via pandoc, but later we'll go
>> into final production...
>
> Sounds interesting. What's your workflow? Do you use a special editor
> (WYSIWYM?) for your markup?
>
> For a new project I'm planning to use some simple markup (probably ReST)
> with a Web CMS to create HTML and ConTeXt -> PDF.
> (I won't need math.)
>
> Greetlings from Lake Constance!
> Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
>
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-08-13 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 11:03 simplefonts or Typecripts Gour D.
2010-08-13 15:58 ` Hans Hagen
2010-08-13 16:50 ` Gour D.
2010-08-13 19:11 ` Gour D.
2010-08-13 20:35 ` other markup to ConTeXt (was: simplefonts or Typecripts) Henning Hraban Ramm
2010-08-13 22:56 ` John Haltiwanger [this message]
2010-08-14 5:19 ` other markup to ConTeXt Gour D.
2010-08-14 9:23 ` Philipp Gesang
2010-08-14 9:31 ` John Haltiwanger
2010-08-14 9:50 ` Khaled Hosny
2010-08-14 9:52 ` Hans Hagen
2010-08-14 10:23 ` Philipp Gesang
2010-08-14 12:47 ` Henning Hraban Ramm
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='AANLkTi=nWNONKgueYLb4CS7o9jR7+r1K3+w-v3+=Sg4S@mail.gmail.com' \
--to=john.haltiwanger@gmail.com \
--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).