This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
RE: What is docbook used for? (faq)
- From: Jens Emmerich <Jens dot Emmerich at encorus-le dot com>
- To: 'Dave Pawson' <daveP at dpawson dot freeserve dot co dot uk>,"'docbook-apps at lists dot oasis-open dot org'" <docbook-apps at lists dot oasis-open dot org>
- Date: Wed, 12 Dec 2001 12:00:00 +0100
- Subject: RE: DOCBOOK-APPS: What is docbook used for? (faq)
We (Encorus Technologies) use a (relatively small) docbook
extension for generating 3 targets from a single source:
1. product API specifications (targeted at internal developers),
2. API refenrence manual (targeted at our customers),
3. API validation code (different programming languages).
Single source is extremely useful here as it makes keeping consistency much
easier.
Plain docbook is used for other specifications and requirements documents.
Jens
> -----Original Message-----
> From: Dave Pawson [mailto:daveP@dpawson.freeserve.co.uk]
> Sent: Samstag, 8. Dezember 2001 10:52
> To: docbook-apps@lists.oasis-open.org
> Subject: DOCBOOK-APPS: What is docbook used for? (faq)
>
>
> Norm had this question asked of him,
> and rather than answer 'what can docbook be used for'
> I'd like to quote concrete examples.
>
> Would you mail me with additions please:
>
> Writing books (for print or web publishing)
> Websites
> Documenting Applications and OS extensions
> xfree86
> ...
> Producing HTML help files
>
> Any generic input appreciated.
>
> TIA, DaveP
>
>