ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: generating html
Date: Wed, 23 Jun 2004 08:41:46 -0600	[thread overview]
Message-ID: <20040623144145.GA27512@swordfish> (raw)
In-Reply-To: <57178.80.58.5.46.1087999460.squirrel@bitmail.bitmailer.com>

On Wed, Jun 23, 2004 at 04:04:20PM +0200, jimarin@bayesinf.com wrote:
> is there an easy way to transform a ConTeXt document into html...?

I searched the archives of this mailing list about a year ago for info
on that subject, and found nothing. So it would appear there is no such
way ... though I didn't investigate very deeply.

What I would do--if I were working with new documents--would be to
create the documents in XML; then I could use ConTeXt for the print
version, and XSLT to generate HTML. XSLT isn't exactly easy, but it is
proven and widely used.

If you need to work with documents that are already in ConTeXt ...  you
know, now that I think about it, it probably wouldn't be very hard to
write a script to translate ConTeXt to XML. Once you've done that
translation,  you use XSLT to output HTML.

Again, not easy, but certainly feasible.

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

  reply	other threads:[~2004-06-23 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 14:04 jimarin
2004-06-23 14:41 ` Matt Gushee [this message]
2004-06-23 16:07 ` Hans Hagen
2004-06-23 17:20   ` Patrick Gundlach
2021-10-11 17:12 Generating HTML Hans Åberg 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=20040623144145.GA27512@swordfish \
    --to=mgushee@havenrock.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).