public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: Where, what and how - The future of DocBook
Date: Tue, 05 Dec 2000 15:53:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0012051509320.2919-100000@localhost> (raw)
Message-ID: <20001205155300.M4RmF7hKHFYO-iCMThIWYivRhfO3Bt8V4vcgWO6U1x8@z> (raw)
In-Reply-To: <Pine.LNX.4.30.0012052258020.1160-100000@pto.sslug>

I am a member of a two-man team that converted a largish piece (more than
100 pages) of technical documentation from latexinfo to DocBook 4.1 XML.
Fortunately, my partner is a real smart cookie so I let him handle most of
the technical end.  I have concentrated on editing the syntax changes with
considerable help from him on doing the routine part of it with scripts.

Since the conversion was completed I have been entering lots of extra
content with an ordinary editor (jed).  I understand there is a great
DocBook interface available with emacs, but I haven't bothered with it yet
because it is not really needed. From my experience I would assert you don't
need any special tool to edit and improve documentation written in DocBook.
The tags that are ordinarily used are easy to memorize.  Of course, it
probably helps that I am a good touch typist. If you don't have that skill I
guess you need to find some tool that gives you WYSIWYG.  But it wasn't
necessary in my case, and I suspect that is true for most documenters.

To move away from this useful but still rather generalized discussion, the
only real concern I have about DocBook at the moment is getting glitch-free
builds of our documentation with Cygnus DocBook 4.1 XML on Redhat 6.2
systems.... ;-)

The major glitch for us is the pdfjadetex command does not work in the
slightest (see my previous postings). I am confident that problem is such a
glaring error with such a simple demonstration that it will be rapidly
solved.  We have no such glitches on our Debian DocBook 4.1 XML system for
building our documentation so it provides a nice comparison to help sort out
problems in the recent 4.1 XML Cygnus version of DocBook.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

  parent reply	other threads:[~2000-12-05 15:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Peter Toft
2000-12-03  9:23 ` Peter Toft
2000-12-27  6:36 ` Norman Walsh
2000-12-04  6:08   ` Norman Walsh
2000-12-27  6:36   ` Peter Toft
2000-12-05 14:12     ` Peter Toft
2000-12-27  6:36     ` Alan W. Irwin [this message]
2000-12-05 15:53       ` Alan W. Irwin
2000-12-27  6:36       ` Michael Smith
2000-12-05 21:27         ` Michael Smith
2000-12-27  6:36         ` Alan W. Irwin
2000-12-05 22:50           ` Alan W. Irwin
2000-12-27  6:36           ` Michael Smith
2000-12-06  0:51             ` Michael Smith
2000-12-27  6:36           ` Gregory Leblanc
2000-12-06  9:39             ` Gregory Leblanc
2000-12-27  6:36         ` Eric Bischoff
2000-12-06  5:23           ` Eric Bischoff
2000-12-27  6:36     ` Jorge Godoy
2000-12-05 16:58       ` Jorge Godoy
2000-12-27  6:36       ` Eric Bischoff
2000-12-06  5:10         ` Eric Bischoff
2000-12-27  6:36         ` Michael Wiedmann
2000-12-06  5:36           ` Michael Wiedmann
2000-12-27  6:36           ` Eric Bischoff
2000-12-06  5:53             ` Eric Bischoff
2000-12-27  6:36             ` Mark Johnson
2000-12-06  8:05               ` Mark Johnson
2000-12-27  6:36               ` Eric Bischoff
2000-12-06  8:15                 ` Eric Bischoff
2000-12-27  6:36         ` madhu
2000-12-15  9:22           ` madhu
2000-12-27  6:36           ` Michael Smith
2000-12-15 10:40             ` Michael Smith
     [not found] <200012061914.UAA08546@mailserv.caiw.nl>
2000-12-27  6:36 ` Hugo.van.der.Kooij
2000-12-06 12:31   ` Hugo.van.der.Kooij
     [not found] <200012061723.KAA06519@gw.estinc.com>
2000-12-27  6:36 ` Craig Boone
2000-12-06 11:06   ` Craig Boone
2000-12-27  6:36   ` Gregory Leblanc
2000-12-06 11:12     ` Gregory Leblanc
     [not found]   ` <200012061858.LAA06946@gw.estinc.com>
2000-12-27  6:36     ` Craig Boone
2000-12-06 11:46       ` Craig Boone
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Pfaffner, Peter
2000-12-05  7:18 ` Pfaffner, Peter
2000-12-27  6:36 Peter Ring
2000-12-05  7:45 ` Peter Ring
2000-12-27  6:36 Peter Ring
2000-12-07  3:45 ` Peter Ring

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=Pine.LNX.4.21.0012051509320.2919-100000@localhost \
    --to=irwin@beluga.phys.uvic.ca \
    --cc=docbook-tools-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).