public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Éric Bischoff" <ebischoff@nerim.net>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: Docbook2ps and jade: too many arguments for function?
Date: Mon, 07 Nov 2005 08:26:00 -0000	[thread overview]
Message-ID: <200511070926.14154.ebischoff@nerim.net> (raw)
In-Reply-To: <115f8a150510281041p19449a27j2593b406649081e5@mail.gmail.com>

Le Vendredi 28 Octobre 2005 19:41, Nathan and Ashley Murray a écrit :
> Im having problems trying to convert my docbook 2 postscript. I think
> the problem may even be in the initial conversion to tex.
>
> I can convert to html with no problems as long as I designate the xml.dcl
> file. Here are my error messages:
>
> docbook2ps --dcl /usr/share/sgml/xml.dcl progress.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet:
> /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print Working on:
> /home/nathan/docs/xml/progress
> .sgml

This carriage return is strange. Have you an embedded carriage return in your 
file name ?

> jade:/usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl:475:2:E:
> too many arguments for function

Strange.

> dvips: ! DVI file can't be opened.
> rm: cannot remove `progress.dvi': No such file or directory
>
> Any thoughts?
> While I'm at it, does anyone know a way I can specify the xml.dcl file
> to be the default?

Have a
	<?xml version="1.0" ?>
at the beginning of your file.


And while we are at it : I noticed that there are still emails like
	Eric Bischoff <eric@caldera.de>
in some files. Can someone please replace them with
	Éric Bischoff <ebischoff@nerim.net>
or with some email of the current maintainers ?


-- 
Marre des virus, vers, spywares, adwares et plantages ?
Passez à Linux !

      reply	other threads:[~2005-11-07  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 17:41 Nathan and Ashley Murray
2005-11-07  8:26 ` Éric Bischoff [this message]

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=200511070926.14154.ebischoff@nerim.net \
    --to=ebischoff@nerim.net \
    --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).