From: Gour <gour@mail.inet.hr>
Subject: Re: DocBookInConTeXt customization?
Date: Sun, 8 Dec 2002 20:54:29 +0100 [thread overview]
Message-ID: <20021208195429.GA20944@inet.hr> (raw)
In-Reply-To: <4224182C-0AC2-11D7-B0AD-0050E4258255@fastmail.fm>
Bruce D'Arcus (bdarcus@fastmail.fm) wrote:
> In my little experience with this, it seems you'd want a module (or is
> an environment better?) that specifies the formatting for the document
> (just as you would for any ConTeXt document). This works perfectly for
> those structures that ConTeXt supports, but not for those that it
> doesn't (author, subtitle, abstract, epigraph, etc., etc.).
I'd like something like:
dic*
DocBook -------> ConTeXt ----> output
*dic = DocBookInConTeXt module
which is similar to XSL toolchain:
xslt fop
DocBook ------> XSL-FO -----> output
with the exception that ConTeXt format is more user-friendly & capable than
xsl-fo format, and produces best quality output.
In this way, we have best of both worlds :-) ie. one can use & automatically
process DocBook-authored documents to get high quality.
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?
Btw, I consider that providing DocBook (xml) as an input format will bring many
more users to ConTeXt because high-quality output is what prevents many to use
DocBook as an authoring tool (besides those who are rich enough to buy
commercial FO engines - mostly corporate users).
With time, one can also expect that DocBookInConText module will get more users'
input and be able to map more DocBook elements.
Sincerely,
Gour
--
Gour
gour@mail.inet.hr
Registered Linux User #278493
next prev parent reply other threads:[~2002-12-08 19:54 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 [this message]
2002-12-08 20:38 ` Bruce D'Arcus
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=20021208195429.GA20944@inet.hr \
--to=gour@mail.inet.hr \
--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).