public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: docbook-tools-discuss@sources.redhat.com
Subject: New version of docbook2man causes errors
Date: Sun, 30 Jan 2005 21:50:00 -0000	[thread overview]
Message-ID: <87oef6oac2.fsf@wilson.rwth-aachen.de> (raw)

Hallöchen!

I installed docbook-utils as a SUSE RPM on my pristine SUSE 9.2
system (v0.6.14).  I had used docbook2man before with the call

    docbook2man --encoding=ISO8859-1 some.xml

however, this doesn't work anymore.  First, the --encoding doesn't
seem to be passed to jade but gives an error.  And secondly, the
script aborts with

bronger@wilson:~/xml/tbook_aktuell/manpages> docbook2man tbtolatex.xml
Using catalogs: /usr/share/sgml/docbook/dsssl-stylesheets-1.78/common/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.78/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.78/dtds/html/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.78/html/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.78/print/catalog, /usr/share/sgml/openjade/catalog, , /etc/sgml/catalog, /usr/share/sgml/CATALOG.docbook-dsssl-stylesheets
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print
Working on: /home/bronger/xml/tbook_aktuell/manpages/tbtolatex.xml
Unknown processing instruction: xml version="1.0" encoding="iso-8859-1" at /usr/share/sgml/docbook/utils-0.6.14/helpers/docbook2man-spec.pl line 1241, <STDIN> line 1.


tbtolatex.xml is a valid DocBook XML document.

All this used to work with my old system.  Are there two variants of
docbook2man around there?  If not, what can I do about these errors?

Thank you!

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus

                 reply	other threads:[~2005-01-30 21:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87oef6oac2.fsf@wilson.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --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).