From: "Bruce D'Arcus" <bdarcus@fastmail.fm>
Subject: Re: DocBookInConTeXt customization?
Date: Sun, 8 Dec 2002 15:38:26 -0500 [thread overview]
Message-ID: <00D3F11B-0AED-11D7-B0AD-0050E4258255@fastmail.fm> (raw)
In-Reply-To: <20021208195429.GA20944@inet.hr>
On Sunday, December 8, 2002, at 02:54 PM, Gour wrote:
> If it is possible to get ConTeXt *.tex file after processing DocBook
> *.xml file
> with DocBookInConTeXt module (of course, for those structures that are
> supportedin it), I'd like to know how?
I think we'd need to use XSLT to get that. My understanding is that
the module simply tells ConTeXt how to process the DocBook code.
Maybe someone will correct me though...
This is why I posted the note about tbook; thinking perhaps the XSL
files from that project -- or from a similar project for DocBook that I
vaguely remember -- could be tweaked to output ConTeXt code...
Bruce
next prev parent reply other threads:[~2002-12-08 20:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 15:12 Gour
2002-12-08 15:32 ` Bruce D'Arcus
2002-12-08 19:54 ` Gour
2002-12-08 20:38 ` Bruce D'Arcus [this message]
2002-12-08 20:48 ` Gour
2002-12-08 21:09 ` Bruce D'Arcus
2002-12-08 21:14 ` Gour
2002-12-09 20:09 ` Simon Pepping
2002-12-10 16:53 ` Gour
2002-12-10 17:04 ` Bruce D'Arcus
2002-12-10 17:49 ` Hans Hagen
2002-12-11 20:46 ` Simon Pepping
2002-12-12 10:34 ` Gour
2002-12-12 11:41 ` Bruce D'Arcus
2002-12-12 12:31 ` Gour
2002-12-12 13:29 ` scarso luigi
2002-12-12 13:49 ` Bruce D'Arcus
2002-12-12 14:22 ` scarso luigi
2002-12-12 20:11 ` Simon Pepping
2002-12-13 12:57 ` scarso luigi
2002-12-13 14:32 ` Hans Hagen
2002-12-17 20:54 ` Simon Pepping
2002-12-18 17:42 ` scarso luigi
2002-12-18 19:56 ` Simon Pepping
2002-12-19 12:54 ` scarso luigi
2002-12-19 8:34 ` Hans Hagen
2002-12-12 20:05 ` Simon Pepping
2002-12-08 20:46 ` Hans Hagen
2002-12-08 21:16 ` Gour
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=00D3F11B-0AED-11D7-B0AD-0050E4258255@fastmail.fm \
--to=bdarcus@fastmail.fm \
--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).