169162 - Bugzilla Guide in pdf or in one html file

Status: RESOLVED WORKSFORME

(Documentation Graveyard :: Web Developer, enhancement)

Description

[Ola Engström]

Hi
Getting a nice printout of the  complete Bugzilla guide would be nice. Presently
the only way to do this is either to print the HTML form of the Guide section by
section or to print the textversion ( informative but ugly).
Getting PDF versions or a one file HTML version is possible from the Linux
Documentation Project but they only have version 2.14.
Regards
/ola

Comment 1

[rudman]

Gerv, I think this goes to you...Lob it back to me if that's not the case. Thanks.

Comment 2

[Gervase Markham [:gerv]]

Which version would you like? I can do big HTML easily. PDF might be a bit more
trouble.

Gerv

Comment 3

[Gervase Markham [:gerv]]

Our docs guru, he say:

 There is no direct conversion for Docbook XML to PS/PDF.  However, there are
several indirect ways to approach this problem:

1.  Use a tool such as "HTMLDOC" to convert to PDF after rendering to HTML
2.  Use "a2ps", another common utility, to convert to postscript from the text
version of the Guide created by Lynx.  Warning, though, this results in very
ugly, plain-text-ish output.  Lots of different options for the conversion,
though.  a2ps is an invaluable utility.
3.  Load the HTML Guide up in Mozilla on a GNU/Linux machine, and print it to a
file.  The file will be .ps, which you can then use ps2pdf on to create PDF.

 Option 3 is the easiest, and the one I use when I want a PDF most times.  I'm
not terrifically familiar with HTMLDOC, nor other html to ps conversion tools. 
The unfortunate thing is that it's not necessarily a portable option for PS or
PDF creation.  The nice thing is, though, on a GNU/Linux system, all you need is
Mozilla & Ghostscript and you are in business.  The ghostscript package on my
Redhat 7.3 system at work is labelled "ghostscript-6.52-8".


Let me know if you want the big HTML version.

Gerv

Comment 4

[Gervase Markham [:gerv]]

He also say:

Sorry to reply twice.  The main reason for writing the Guide in Docbook XML in
the first reason was so that it could be included in the Linux Documentation
Project.  I figured (and still do) that if a project is on the Linuxdoc Guides
or Howtos list, you'll get wider dissemination and awareness of the project. 
Anyway, my process for making a file into ps/pdf using mozilla + ps2pdf is
flawed.  The table of contents, index, and glossary won't match the page
numbers, although the formatting would otherwise be OK  Here's the real
solution, available at linuxdoc:

http://www.tldp.org/authors/index.html

Down at the bottom of the page, it goes into a little bit of detail on how they
do it at Linuxdoc.  It appears they use a combination of  a custom script,
ldp_print, plus the htmldoc utility I mentioned in the previous message.  The
heading of the passage is "PDF/Postscript Output".

At the very least, that's the "official" way Linuxdoc updates it. Alternatively,
you can get an updated version by submitting the updated Guide to LDP, and
they'll do it for you.  Don't try to use their email gateway on The Bugzilla
Guide, though, it chokes on the multiple file input. 

Comment 5

[Gervase Markham [:gerv]]

[e-mail] - is there more we can help you with, or can this
bug be closed?

Gerv

Comment 6

[Ola Engström]

This case can be closed.
Thanks for your help.
We are now implementing Bugzilla as a trial for a small helpdesk system.
Where do I post experiences, thoughts and the like - if you want them that is.
I'm as you have already understood more of a happy amateur but with some very
professional backing. /ola 

Comment 7

[Gervase Markham [:gerv]]

WORKSFORME.

Gerv