public inbox for
 help / color / mirror / Atom feed
From: Espen Carlsen <>
To: Eric Bischoff <>
Cc: <>
Subject: SV: Error in docbook2html if source catalog contains spaces.
Date: Mon, 23 Aug 2010 12:55:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

> From: Eric Bischoff []
> > Thought you guys wanted to see this, as you're the one maintaining docbook-utils:
> >
> > The error in line 273 occurs if you have a your .docbook file is in a path that contains a space somewhere in the path and you run docbook2html from the .docbook source directory.
> > example:
> > /home/my test/docbook/ is the current directory and you have a test.docbook file in that folder.
> > Then while you're still in that folder, run docbook2html test.docbook
> > This generates the error in line 273.
> Probably missing quotes around the path...
> Problem is : who currently maintains docbook-utils ? I don't know if I even still have an account, and on which site?

When I searched around, I came up with:

Those looks like mirrors of eachother and the mailaddress at the bottom was the one I mailed.

> If no one show up, I can investigate and see if I can regain access, but it's been years i have not touched those files.
> Best thing would be if someone could proclam himself/herself as the new maintainer.

I think it looks like someone at redhat, though nothing has been changed in those scripts for some years, so it might be that it doesn't have a maintainer.

Espen Carlsen.

  reply	other threads:[~2010-08-23 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 11:41 Espen Carlsen
2010-08-17  9:07 ` Eric Bischoff
2010-08-23 12:55   ` Espen Carlsen [this message]
2010-08-23 13:08     ` SV: " Eric Bischoff

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).