From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: DocBook
Date: Wed, 2 Jan 2002 21:36:42 +0100 [thread overview]
Message-ID: <20020102213642.A1059@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20020101132004.0321ffc0@server-1>; from pragma@wxs.nl on Tue, Jan 01, 2002 at 01:22:03PM +0100
On Tue, Jan 01, 2002 at 01:22:03PM +0100, Hans Hagen wrote:
> At 12:26 PM 12/30/2001 +0100, Simon Pepping wrote:
> >The idea has crossed my mind as well. Docbook has become the standard
> >for all sorts of technical documentation, and it would be nice if such
> >documentation could be formatted using Context. But it is a huge
> >undertaking indeed. One should start on a subset, there should be
> >agreement on which subset, and one should be prepared for a long
> >lasting project.
>
> starting from a subset is doable; is there such a subset known? a quick
> look into the oreilly's docbook book shows a lot of (probably never used)
> stuff,
Not really. I guess article and book as document element are most
popular. But beyond that one has to make a choice which elements are
most relevant. There are indeed many elements which seem only useful
in exceptional cases.
I am currently getting some practice with XML in Context by creating a
mapping for a DocBook file by myself. Until now it is surprisingly
easy. The XML interface works fine. I guess it will become more
difficult if one needs to account for elements whose presence or
absence influences the layout.
Perhaps it would be best to take a number of existing DocBook
documentation files and construct a mapping that works for all of
them. That would give a mapping that might work for many elements and
that could be expanded gradually.
Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2002-01-02 20:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 18:21 DocBook Lukas Kubin
2001-12-05 19:36 ` DocBook Marco Kuhlmann
2001-12-05 20:13 ` DocBook Berend de Boer
2001-12-30 11:26 ` DocBook Simon Pepping
2002-01-01 12:22 ` DocBook Hans Hagen
2002-01-02 20:36 ` Simon Pepping [this message]
2002-01-03 22:42 ` DocBook Matthias Klose
2002-01-04 11:20 ` DocBook Hans Hagen
2002-01-06 20:12 ` DocBook Simon Pepping
2001-12-11 23:01 docbook Hans Hagen
[not found] <200201211101.MAA17323@smail.let.uu.nl>
2002-01-21 20:58 ` docbook Hans Hagen
2012-12-18 11:31 DocBook Roger Mason
2012-12-18 11:47 ` DocBook Wolfgang Schuster
2012-12-18 13:21 ` DocBook Hans Hagen
2012-12-18 16:15 ` DocBook Roger Mason
2012-12-18 12:30 ` DocBook Thomas Weißschuh
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=20020102213642.A1059@scaprea \
--to=spepping@scaprea.hobby.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).