From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: authoring for web and print - suggestions
Date: Sat, 11 May 2013 13:08:23 +0200 [thread overview]
Message-ID: <518E26A7.1090207@uni-bonn.de> (raw)
In-Reply-To: <20130511102651.GA22952@gamma.logic.tuwien.ac.at>
On 05/11/2013 12:26 PM, Norbert Preining wrote:
> Does anyone have experience with authoring for web and print. I.e.,
> we want to maintain only one format and generate both web pages and
> printed documentation from it. Is there intrinsic or through addons
> support in ConteXt for this?
>
> Any suggestion would be greatly welcome
I think the most natural route would be to author your content in
generic xml. This can be wonderfully processed in ConTeXt, and you can
use XSLT to produce xhtml. In theory, you could also directly process
xhtml in ConTeXt, but personally (mind you, I'm no authority on these
questions at all) writing xml (such as docbook) gives you more wiggle
room, should you ever want to reuse your content (just think your
organization uses a new CMS, and you need a different form of html).
Thomas
___________________________________________________________________________________
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:[~2013-05-11 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 10:26 Norbert Preining
2013-05-11 11:08 ` Thomas A. Schmitz [this message]
2013-05-11 12:35 ` Ondřej Hošek
2013-05-11 12:47 ` Grant Rettke
2013-05-11 12:54 ` Hans Hagen
2013-05-11 12:59 ` Grant Rettke
2013-05-11 14:29 ` Martin Schröder
2013-05-13 20:18 ` Mica Semrick
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=518E26A7.1090207@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).