public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Whitis <whitis@freelabs.com>
To: <docbook-tools-discuss@sources.redhat.com>
Subject: BUG: docbook2html --nochunks
Date: Tue, 09 Apr 2002 17:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0204090020170.1590-100000@cervantes.freelabs.com> (raw)
Message-ID: <20020409175700.ic_z72jTEHERqN8vGN8uocAxn729BfENvUQ6sT15ZF4@z> (raw)

If you tell docbook2html not to blow chunks, it writes the output
html document to standard out.   This is fine except for the fact
that it also outputs status messages to standard out (instead
of sending them to stderr where the belong).  So you end up
with an invalid document because the status messages are mixed in.

So, you get stuff like this:
   Using catalogs: /etc/sgml/sgml-docbook-4.0.cat
   Using stylesheet: /usr/share/sgml/docbook/utils-0.6/docbook-utils.dsl#html
   Working on: /home/whitis/docbook/sample.docbook
   [...]
   Done.


--
Mark Whitis   http://www.freelabs.com/~whitis/       NO SPAM
Author of many open source software packages.
Coauthor: Linux Programming Unleashed (1st Edition)

             reply	other threads:[~2002-04-10  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 19:23 Mark Whitis [this message]
2002-04-09 17:57 ` Mark Whitis
2002-12-20 19:23 ` Éric Bischoff
2002-04-09 23:57   ` Éric Bischoff
2002-12-20 19:23   ` Tim Waugh
2002-04-10  0:03     ` Tim Waugh
2002-12-20 19:23     ` multiple bugs and security hole (was: Re: BUG: docbook2html --nochunks) Mark Whitis
2002-04-10 19:40       ` Mark Whitis
2002-12-20 19:23       ` New location of the "Crash Course.to DocBook" Éric Bischoff
2002-04-11  3:25         ` Éric Bischoff
2002-12-20 19:23       ` multiple bugs and security hole (was: Re: BUG: docbook2html --nochunks) Tim Waugh
2002-04-11  7:17         ` Tim Waugh

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.33.0204090020170.1590-100000@cervantes.freelabs.com \
    --to=whitis@freelabs.com \
    --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).