-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Neil Roeth <[EMAIL PROTECTED]> writes:

> On May 30, Neil Roeth ([EMAIL PROTECTED]) wrote:
>  > On May 30, Roger Leigh ([EMAIL PROTECTED]) wrote:
>  >  > 
>  >  > Neil Roeth <[EMAIL PROTECTED]> writes:
>  >  > 
>  >  > [gnupg-doc]
>  >  > > I'm not having much luck.  I do not see anywhere in the DocBook 
> stylesheets
>  >  > > where it does not use the value of the variable %html-ext% for the 
> html file
>  >  > > extension.
>  >  > 
>  >  > Very odd.  It last built on Mon, 1 Nov 2004, according to the
>  >  > changelog, and hasn't changed since.  I assume from this there must
>  >  > have been a change on the docbook tools that broke it somehow.
>  >  > 
>  >  > > I did notice that this document is using a very old version of 
> DocBook, and
>  >  > > it's possible that the DocBook stylesheets are no longer compatible 
> with that.
>  >  > 
>  >  > I tried with the 4.1 DTD.  It processed with warnings (I removed
>  >  > obsolete docinfo elements), but still generated .htm.
>  >  > 
>  >  > > I'll keep looking into it.
>  > 
>  > I'm making some progress.  In gph/db2any, I changed all occurrences of 
> jade to
>  > openjade and added a command line option -V '(define %html-ext% ".html")' 
> and
>  > that made the extension stick.  I also changed all occurrences of nsgmls to
>  > onsgmls and sgml2xml to osx, since those are the names of the commands in
>  > OpenSP corresponding to the older SP commands.  This would require changing
>  > the build dependencies form jade and sp to openjade1.3 and opensp.  Be
>  > forewarned that openjade takes a lot longer to run than jade.  I do not
>  > understand why the equivalent redefinition of %html-ext% in the
>  > gph/common/gph-style.dsl stylesheet does not seem effective.  I'll 
> continue to
>  > work on it some more to get it down to the necessary changes to make it 
> work -
>  > I hesitate to send you what I have at the moment because I changed a 
> number of
>  > things for debugging, etc., many of which I am sure are unnecessary.
>  > 
>  > BTW, I noticed that the db2any script appears to move html files around, 
> but
>  > there is an %output-dir% variable that can be used to do the equivalent.  
> This
>  > could be used to simplify the script - probably best left until post-Sarge.
>
> Here's a diff for db2any that will create the files with the html extension.
> You'll need to change the build dependencies as mentioned above.

Many thanks.  I did a bit more testing, and created a diff for it,
including all your changes (its in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310763 and the final
packages are at http://people.debian.org/~rleigh/).  Unfortunately,
the maintainer has not used this patch, instead fixing the problem by
renaming the files by hand, presumably because the change is much
smaller and easier to verify for sarge.  Hopefully this can be
corrected using your patch post-sarge.

I verified the documents of all of the different languages, and didn't
see any problems with the openjade output.

> I also noticed that chapters 6 and 7 were commented out in manual.sgml, not
> sure why, that led to additional errors, and uncommenting them didn't seem to
> cause problems.
>
> I'd be happy to help update the document to a newer version of DocBook and use
> the built in features to place the html output directly into the desired
> directory instead of the hacks in db2any after the Sarge release.

I'm not the maintainer of the package (it's maintained by James
Troup), so this is to let him know of your offer, which I'm sure will
be well appreciated!


Many thanks for all your work,
Roger

- -- 
Roger Leigh
                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                Debian GNU/Linux        http://www.debian.org/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFCnfIhVcFcaSW/uEgRAg2WAJ9A9dYjztcYGnN+k63xT/3D1C56mgCdENqA
Gr71VQRJ6nBVFcK/XNFxWJw=
=hnDX
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to