Recompiled docs for release

2003-11-02 02:00:11 +00:00 · 2003-11-02 02:00:11 +00:00 · 85205d41f0
--- a/webtools/bugzilla/docs/html/Bugzilla-Guide.html
+++ b/webtools/bugzilla/docs/html/Bugzilla-Guide.html
--- a/webtools/bugzilla/docs/html/about.html
+++ b/webtools/bugzilla/docs/html/about.html
@ -4,7 +4,8 @@
 >About This Guide</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="chapter"
 ><H1
 ><A
-NAME="about"
-></A
->Chapter 1. About This Guide</H1
+NAME="about">Chapter 1. About This Guide</H1
 ><DIV
 CLASS="TOC"
 ><DL
--- a/webtools/bugzilla/docs/html/administration.html
+++ b/webtools/bugzilla/docs/html/administration.html
@ -4,7 +4,8 @@
 >Administering Bugzilla</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="chapter"
 ><H1
 ><A
-NAME="administration"
-></A
->Chapter 5. Administering Bugzilla</H1
+NAME="administration">Chapter 5. Administering Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
@ -179,22 +178,22 @@ HREF="cust-templates.html"
 ><DL
 ><DT
 >5.7.1. <A
-HREF="cust-templates.html#AEN1570"
+HREF="cust-templates.html#AEN1604"
 >What to Edit</A
 ></DT
 ><DT
 >5.7.2. <A
-HREF="cust-templates.html#AEN1593"
+HREF="cust-templates.html#AEN1627"
 >How To Edit Templates</A
 ></DT
 ><DT
 >5.7.3. <A
-HREF="cust-templates.html#AEN1603"
+HREF="cust-templates.html#AEN1637"
 >Template Formats</A
 ></DT
 ><DT
 >5.7.4. <A
-HREF="cust-templates.html#AEN1616"
+HREF="cust-templates.html#AEN1650"
 >Particular Templates</A
 ></DT
 ><DT
--- a/webtools/bugzilla/docs/html/cmdline.html
+++ b/webtools/bugzilla/docs/html/cmdline.html
@ -4,7 +4,8 @@
 >Command-line Bugzilla Queries</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -75,9 +76,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="cmdline"
-></A
->C.2. Command-line Bugzilla Queries</H1
+NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
 ><P
 >There are a suite of Unix utilities for querying Bugzilla from the 
    command line. They live in the 
--- a/webtools/bugzilla/docs/html/conventions.html
+++ b/webtools/bugzilla/docs/html/conventions.html
@ -4,7 +4,8 @@
 >Document Conventions</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,17 +73,13 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="conventions"
-></A
->1.5. Document Conventions</H1
+NAME="conventions">1.5. Document Conventions</H1
 ><P
 >This document uses the following conventions:</P
 ><DIV
 CLASS="informaltable"
 ><A
-NAME="AEN111"
-></A
-><P
+NAME="AEN111"><P
 ></P
 ><TABLE
 BORDER="0"
--- a/webtools/bugzilla/docs/html/copyright.html
+++ b/webtools/bugzilla/docs/html/copyright.html
@ -4,7 +4,8 @@
 >Copyright Information</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,13 +73,9 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="copyright"
-></A
->1.1. Copyright Information</H1
+NAME="copyright">1.1. Copyright Information</H1
 ><A
-NAME="AEN33"
-></A
-><TABLE
+NAME="AEN33"><TABLE
 BORDER="0"
 WIDTH="100%"
 CELLSPACING="0"
--- a/webtools/bugzilla/docs/html/credits.html
+++ b/webtools/bugzilla/docs/html/credits.html
@ -4,7 +4,8 @@
 >Credits</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="credits"
-></A
->1.4. Credits</H1
+NAME="credits">1.4. Credits</H1
 ><P
 >&#13;      The people listed below have made enormous contributions to the
      creation of this Guide, through their writing, dedicated hacking efforts,
--- a/webtools/bugzilla/docs/html/cust-change-permissions.html
+++ b/webtools/bugzilla/docs/html/cust-change-permissions.html
@ -4,7 +4,8 @@
 >Change Permission Customization</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="cust-change-permissions"
-></A
->5.8. Change Permission Customization</H1
+NAME="cust-change-permissions">5.8. Change Permission Customization</H1
 ><DIV
 CLASS="warning"
 ><P
--- a/webtools/bugzilla/docs/html/cust-templates.html
+++ b/webtools/bugzilla/docs/html/cust-templates.html
@ -4,7 +4,8 @@
 >Template Customization</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="cust-templates"
-></A
->5.7. Template Customization</H1
+NAME="cust-templates">5.7. Template Customization</H1
 ><P
 >&#13;      One of the large changes for 2.16 was the templatization of the
      entire user-facing UI, using the 
@ -102,9 +101,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1570"
-></A
->5.7.1. What to Edit</H2
+NAME="AEN1604">5.7.1. What to Edit</H2
 ><P
 >&#13;        There are two different ways of editing of Bugzilla's templates,
        and which you use depends mainly on how you upgrade Bugzilla. The
@ -252,9 +249,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1593"
-></A
->5.7.2. How To Edit Templates</H2
+NAME="AEN1627">5.7.2. How To Edit Templates</H2
 ><P
 >&#13;        The syntax of the Template Toolkit language is beyond the scope of
        this guide. It's reasonably easy to pick up by looking at the current 
@ -334,9 +329,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1603"
-></A
->5.7.3. Template Formats</H2
+NAME="AEN1637">5.7.3. Template Formats</H2
 ><P
 >&#13;        Some CGIs have the ability to use more than one template. For
        example, buglist.cgi can output bug lists as RDF or two
@ -396,9 +389,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1616"
-></A
->5.7.4. Particular Templates</H2
+NAME="AEN1650">5.7.4. Particular Templates</H2
 ><P
 >&#13;        There are a few templates you may be particularly interested in
        customizing for your installation.
@ -585,9 +576,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="template-http-accept"
-></A
->5.7.5. Configuring Bugzilla to Detect the User's Language</H2
+NAME="template-http-accept">5.7.5. Configuring Bugzilla to Detect the User's Language</H2
 ><P
 >Begining in version 2.18 (first introduced in version 
      2.17.4), it's now possible to have the users web browser tell Bugzilla
--- a/webtools/bugzilla/docs/html/database.html
+++ b/webtools/bugzilla/docs/html/database.html
@ -4,7 +4,8 @@
 >The Bugzilla Database</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="appendix"
 ><H1
 ><A
-NAME="database"
-></A
->Appendix B. The Bugzilla Database</H1
+NAME="database">Appendix B. The Bugzilla Database</H1
 ><DIV
 CLASS="TOC"
 ><DL
--- a/webtools/bugzilla/docs/html/dbdoc.html
+++ b/webtools/bugzilla/docs/html/dbdoc.html
@ -4,7 +4,8 @@
 >MySQL Bugzilla Database Introduction</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="dbdoc"
-></A
->B.2. MySQL Bugzilla Database Introduction</H1
+NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
 ><P
 >This information comes straight from my life. I was forced to learn
    how Bugzilla organizes database because of nitpicky requests from users
@ -134,9 +133,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN2236"
-></A
->B.2.1. Bugzilla Database Basics</H2
+NAME="AEN2277">B.2.1. Bugzilla Database Basics</H2
 ><P
 >If you were like me, at this point you're totally clueless about
      the internals of MySQL, and if it weren't for this executive order from
@ -248,9 +245,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN2263"
-></A
->B.2.1.1. Bugzilla Database Tables</H3
+NAME="AEN2304">B.2.1.1. Bugzilla Database Tables</H3
 ><P
 >Imagine your MySQL database as a series of spreadsheets, and
        you won't be too far off. If you use this command:</P
--- a/webtools/bugzilla/docs/html/dbmodify.html
+++ b/webtools/bugzilla/docs/html/dbmodify.html
@ -4,7 +4,8 @@
 >Modifying Your Running System</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="dbmodify"
-></A
->B.1. Modifying Your Running System</H1
+NAME="dbmodify">B.1. Modifying Your Running System</H1
 ><P
 >Bugzilla optimizes database lookups by storing all relatively
      static information in the 
--- a/webtools/bugzilla/docs/html/disclaimer.html
+++ b/webtools/bugzilla/docs/html/disclaimer.html
@ -4,7 +4,8 @@
 >Disclaimer</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="disclaimer"
-></A
->1.2. Disclaimer</H1
+NAME="disclaimer">1.2. Disclaimer</H1
 ><P
 >&#13;      No liability for the contents of this document can be accepted.
      Use the concepts, examples, and other content at your own risk.
--- a/webtools/bugzilla/docs/html/extraconfig.html
+++ b/webtools/bugzilla/docs/html/extraconfig.html
@ -4,7 +4,8 @@
 >Optional Additional Configuration</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,17 +73,13 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="extraconfig"
-></A
->4.2. Optional Additional Configuration</H1
+NAME="extraconfig">4.2. Optional Additional Configuration</H1
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN796"
-></A
->4.2.1. Dependency Charts</H2
+NAME="AEN830">4.2.1. Dependency Charts</H2
 ><P
 >As well as the text-based dependency graphs, Bugzilla also
      supports dependency graphing, using a package called 'dot'.
@ -144,9 +141,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN811"
-></A
->4.2.2. Bug Graphs</H2
+NAME="AEN845">4.2.2. Bug Graphs</H2
 ><P
 >As long as you installed the GD and Graph::Base Perl modules you
      might as well turn on the nifty Bugzilla bug reporting graphs.</P
@ -203,9 +198,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN824"
-></A
->4.2.3. The Whining Cron</H2
+NAME="AEN858">4.2.3. The Whining Cron</H2
 ><P
 >By now you have a fully functional Bugzilla, but what good are
      bugs if they're not annoying? To help make those bugs more annoying you
@ -292,9 +285,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="bzldap"
-></A
->4.2.4. LDAP Authentication</H2
+NAME="bzldap">4.2.4. LDAP Authentication</H2
 ><DIV
 CLASS="note"
 ><P
@ -413,9 +404,7 @@ CLASS="variablelist"
 ><DL
 ><DT
 ><A
-NAME="param-loginmethod"
-></A
->loginmethod</DT
+NAME="param-loginmethod">loginmethod</DT
 ><DD
 ><P
 >This parameter should be set to <SPAN
@ -444,9 +433,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="param-LDAPserver"
-></A
->LDAPserver</DT
+NAME="param-LDAPserver">LDAPserver</DT
 ><DD
 ><P
 >This parameter should be set to the name (and optionally the
@ -466,9 +453,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="param-LDAPbinddn"
-></A
->LDAPbinddn [Optional]</DT
+NAME="param-LDAPbinddn">LDAPbinddn [Optional]</DT
 ><DD
 ><P
 >Some LDAP servers will not allow an anonymous bind to search
@ -484,9 +469,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="param-LDAPBaseDN"
-></A
->LDAPBaseDN</DT
+NAME="param-LDAPBaseDN">LDAPBaseDN</DT
 ><DD
 ><P
 >The LDAPBaseDN parameter should be set to the location in
@ -501,9 +484,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="param-LDAPuidattribute"
-></A
->LDAPuidattribute</DT
+NAME="param-LDAPuidattribute">LDAPuidattribute</DT
 ><DD
 ><P
 >The LDAPuidattribute parameter should be set to the attribute
@ -519,9 +500,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="param-LDAPmailattribute"
-></A
->LDAPmailattribute</DT
+NAME="param-LDAPmailattribute">LDAPmailattribute</DT
 ><DD
 ><P
 >The LDAPmailattribute parameter should be the name of the
@ -542,9 +521,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="content-type"
-></A
->4.2.5. Preventing untrusted Bugzilla content from executing malicious
+NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
      Javascript code</H2
 ><P
 >It is possible for a Bugzilla to execute malicious Javascript
@ -648,9 +625,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="directoryindex"
-></A
->4.2.6. <TT
+NAME="directoryindex">4.2.6. <TT
 CLASS="filename"
 >directoryindex</TT
 > for the Bugzilla default page.</H2
@ -675,9 +650,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="mod_perl"
-></A
->4.2.7. Bugzilla and <TT
+NAME="mod_perl">4.2.7. Bugzilla and <TT
 CLASS="filename"
 >mod_perl</TT
 ></H2
@ -692,9 +665,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="mod-throttle"
-></A
->4.2.8. <TT
+NAME="mod-throttle">4.2.8. <TT
 CLASS="filename"
 >mod_throttle</TT
 >
--- a/webtools/bugzilla/docs/html/faq.html
+++ b/webtools/bugzilla/docs/html/faq.html
@ -4,7 +4,8 @@
 >The Bugzilla FAQ</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="appendix"
 ><H1
 ><A
-NAME="faq"
-></A
->Appendix A. The Bugzilla FAQ</H1
+NAME="faq">Appendix A. The Bugzilla FAQ</H1
 ><P
 >&#13;    This FAQ includes questions not covered elsewhere in the Guide.
  </P
@ -519,6 +518,12 @@ HREF="faq.html#faq-use-keyword"
 >&#13;	    How do I change a keyword in Bugzilla, once some bugs are using it?
 	  </A
 ></DT
+><DT
+>A.7.6. <A
+HREF="faq.html#faq-use-close"
+>&#13;        Why can't I close bugs from the "Change Several Bugs at Once" page?
+      </A
+></DT
 ></DL
 ></DD
 ><DT
@ -560,18 +565,14 @@ HREF="faq.html#faq-hacking-patches"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-general"
-></A
->1. General Questions</H3
+NAME="faq-general">1. General Questions</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-information"
-></A
-><B
+NAME="faq-general-information"><B
 >A.1.1. </B
 >
 	    Where can I find information about Bugzilla?</P
@ -597,9 +598,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-license"
-></A
-><B
+NAME="faq-general-license"><B
 >A.1.2. </B
 >
 	    What license is Bugzilla distributed under?
@ -626,9 +625,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-support"
-></A
-><B
+NAME="faq-general-support"><B
 >A.1.3. </B
 >
 	    How do I get commercial support for Bugzilla?
@ -672,9 +669,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-companies"
-></A
-><B
+NAME="faq-general-companies"><B
 >A.1.4. </B
 >
 	    What major companies or projects are currently using Bugzilla
@ -719,9 +714,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-maintainers"
-></A
-><B
+NAME="faq-general-maintainers"><B
 >A.1.5. </B
 >
 	    Who maintains Bugzilla?
@ -749,9 +742,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-compare"
-></A
-><B
+NAME="faq-general-compare"><B
 >A.1.6. </B
 >
 	    How does Bugzilla stack up against other bug-tracking databases?
@ -787,9 +778,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-bzmissing"
-></A
-><B
+NAME="faq-general-bzmissing"><B
 >A.1.7. </B
 >
 	    Why doesn't Bugzilla offer this or that feature or compatibility
@ -827,9 +816,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-mysql"
-></A
-><B
+NAME="faq-general-mysql"><B
 >A.1.8. </B
 >
 	    Why MySQL?  I'm interested in seeing Bugzilla run on
@ -872,9 +859,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-bonsaitools"
-></A
-><B
+NAME="faq-general-bonsaitools"><B
 >A.1.9. </B
 >
 	    What is <TT
@ -914,9 +899,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-perlpath"
-></A
-><B
+NAME="faq-general-perlpath"><B
 >A.1.10. </B
 >
            My perl is not located at <TT
@ -963,9 +946,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-general-cookie"
-></A
-><B
+NAME="faq-general-cookie"><B
 >A.1.11. </B
 >
 	    Is there an easy way to change the Bugzilla cookie name?
@ -986,9 +967,7 @@ CLASS="answer"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-phb"
-></A
->2. Managerial Questions</H3
+NAME="faq-phb">2. Managerial Questions</H3
 ><P
 >&#13;	<DIV
 CLASS="note"
@ -1025,9 +1004,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-client"
-></A
-><B
+NAME="faq-phb-client"><B
 >A.2.1. </B
 >
 	    Is Bugzilla web-based, or do you have to have specific software or
@ -1051,9 +1028,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-integration"
-></A
-><B
+NAME="faq-phb-integration"><B
 >A.2.2. </B
 >
 	    Can Bugzilla integrate with
@ -1077,9 +1052,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-projects"
-></A
-><B
+NAME="faq-phb-projects"><B
 >A.2.3. </B
 >
 	    Does Bugzilla allow the user to track multiple projects?
@ -1102,9 +1075,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-sorting"
-></A
-><B
+NAME="faq-phb-sorting"><B
 >A.2.4. </B
 >
 	    If I am on many projects, and search for all bugs assigned to me, will
@ -1127,9 +1098,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-attachments"
-></A
-><B
+NAME="faq-phb-attachments"><B
 >A.2.5. </B
 >
 	    Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
@ -1156,9 +1125,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-priorities"
-></A
-><B
+NAME="faq-phb-priorities"><B
 >A.2.6. </B
 >
 	    Does Bugzilla allow us to define our own priorities and levels? Do we
@ -1193,9 +1160,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-reporting"
-></A
-><B
+NAME="faq-phb-reporting"><B
 >A.2.7. </B
 >
 	    Does Bugzilla provide any reporting features, metrics, graphs, etc? You
@ -1231,9 +1196,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-email"
-></A
-><B
+NAME="faq-phb-email"><B
 >A.2.8. </B
 >
 	    Is there email notification and if so, what do you see when you get an
@ -1258,9 +1221,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-cclist"
-></A
-><B
+NAME="faq-phb-cclist"><B
 >A.2.9. </B
 >
 	    Can email notification be set up to send to multiple
@ -1283,9 +1244,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-emailapp"
-></A
-><B
+NAME="faq-phb-emailapp"><B
 >A.2.10. </B
 >
 	    Do users have to have any particular
@ -1342,9 +1301,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-data"
-></A
-><B
+NAME="faq-phb-data"><B
 >A.2.11. </B
 >
 	    Does Bugzilla allow data to be imported and exported? If I had outsiders
@ -1404,9 +1361,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-l10n"
-></A
-><B
+NAME="faq-phb-l10n"><B
 >A.2.12. </B
 >
 	    Has anyone converted Bugzilla to another language to be used in other
@ -1442,9 +1397,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-reports"
-></A
-><B
+NAME="faq-phb-reports"><B
 >A.2.13. </B
 >
 	    Can a user create and save reports? Can they do this in Word format?
@ -1467,9 +1420,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-searching"
-></A
-><B
+NAME="faq-phb-searching"><B
 >A.2.14. </B
 >
 	    Does Bugzilla have the ability to search by word, phrase, compound
@ -1493,9 +1444,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-midair"
-></A
-><B
+NAME="faq-phb-midair"><B
 >A.2.15. </B
 >
 	     Does Bugzilla provide record locking when there is simultaneous access
@ -1520,9 +1469,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-backup"
-></A
-><B
+NAME="faq-phb-backup"><B
 >A.2.16. </B
 >
 	    Are there any backup features provided?
@ -1550,9 +1497,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-livebackup"
-></A
-><B
+NAME="faq-phb-livebackup"><B
 >A.2.17. </B
 >
 	    Can users be on the system while a backup is in progress?
@ -1576,9 +1521,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-maintenance"
-></A
-><B
+NAME="faq-phb-maintenance"><B
 >A.2.18. </B
 >
 	    What type of human resources are needed to be on staff to install and
@ -1611,9 +1554,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-installtime"
-></A
-><B
+NAME="faq-phb-installtime"><B
 >A.2.19. </B
 >
 	    What time frame are we looking at if we decide to hire people to install
@ -1644,9 +1585,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-phb-cost"
-></A
-><B
+NAME="faq-phb-cost"><B
 >A.2.20. </B
 >
 	    Is there any licensing fee or other fees for using Bugzilla? Any
@ -1669,18 +1608,14 @@ CLASS="answer"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-security"
-></A
->3. Bugzilla Security</H3
+NAME="faq-security">3. Bugzilla Security</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-security-mysql"
-></A
-><B
+NAME="faq-security-mysql"><B
 >A.3.1. </B
 >
 	    How do I completely disable MySQL security if it's giving me problems
@ -1707,9 +1642,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-security-knownproblems"
-></A
-><B
+NAME="faq-security-knownproblems"><B
 >A.3.2. </B
 >
 	    Are there any security problems with Bugzilla?
@ -1735,9 +1668,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-security-mysqluser"
-></A
-><B
+NAME="faq-security-mysqluser"><B
 >A.3.3. </B
 >
 	    I've implemented the security fixes mentioned in Chris Yeh's security
@ -1762,18 +1693,14 @@ CLASS="answer"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-email"
-></A
->4. Bugzilla Email</H3
+NAME="faq-email">4. Bugzilla Email</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-nomail"
-></A
-><B
+NAME="faq-email-nomail"><B
 >A.4.1. </B
 >
 	    I have a user who doesn't want to receive any more email from Bugzilla.
@ -1801,9 +1728,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-testing"
-></A
-><B
+NAME="faq-email-testing"><B
 >A.4.2. </B
 >
 	    I'm evaluating/testing Bugzilla, and don't want it to send email to
@ -1827,9 +1752,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-whine"
-></A
-><B
+NAME="faq-email-whine"><B
 >A.4.3. </B
 >
 	    I want whineatnews.pl to whine at something more, or other than, only new
@ -1860,9 +1783,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-procmail"
-></A
-><B
+NAME="faq-email-procmail"><B
 >A.4.4. </B
 >
 	    I don't like/want to use Procmail to hand mail off to bug_email.pl.
@ -1878,9 +1799,7 @@ CLASS="answer"
 	    You can call bug_email.pl directly from your aliases file, with
 	    an entry like this:
 	    <A
-NAME="AEN2031"
-></A
-><BLOCKQUOTE
+NAME="AEN2065"><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
 ><P
 >&#13;		bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
@ -1899,9 +1818,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-mailif"
-></A
-><B
+NAME="faq-email-mailif"><B
 >A.4.5. </B
 >
 	    How do I set up the email interface to submit/change bugs via email?
@ -1924,9 +1841,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-sendmailnow"
-></A
-><B
+NAME="faq-email-sendmailnow"><B
 >A.4.6. </B
 >
 	    Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
@ -1985,9 +1900,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-email-nonreceived"
-></A
-><B
+NAME="faq-email-nonreceived"><B
 >A.4.7. </B
 >
 	     How come email from Bugzilla changes never reaches me?
@ -2016,18 +1929,14 @@ CLASS="answer"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-db"
-></A
->5. Bugzilla Database</H3
+NAME="faq-db">5. Bugzilla Database</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-db-oracle"
-></A
-><B
+NAME="faq-db-oracle"><B
 >A.5.1. </B
 >
 	    I've heard Bugzilla can be used with Oracle?
@ -2053,9 +1962,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-db-corrupted"
-></A
-><B
+NAME="faq-db-corrupted"><B
 >A.5.2. </B
 >
 	    I think my database might be corrupted, or contain invalid entries. What
@ -2100,9 +2007,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-db-manualedit"
-></A
-><B
+NAME="faq-db-manualedit"><B
 >A.5.3. </B
 >
 	    I want to manually edit some entries in my database. How?
@ -2141,9 +2046,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-db-permissions"
-></A
-><B
+NAME="faq-db-permissions"><B
 >A.5.4. </B
 >
 	    I think I've set up MySQL permissions correctly, but Bugzilla still can't
@ -2202,9 +2105,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-db-synchronize"
-></A
-><B
+NAME="faq-db-synchronize"><B
 >A.5.5. </B
 >
 	    How do I synchronize bug information among multiple different Bugzilla
@ -2239,18 +2140,14 @@ CLASS="answer"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-nt"
-></A
->6. Bugzilla and Win32</H3
+NAME="faq-nt">6. Bugzilla and Win32</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-nt-easiest"
-></A
-><B
+NAME="faq-nt-easiest"><B
 >A.6.1. </B
 >
 	    What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
@ -2273,9 +2170,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-nt-bundle"
-></A
-><B
+NAME="faq-nt-bundle"><B
 >A.6.2. </B
 >
 	    Is there a "Bundle::Bugzilla" equivalent for Win32?
@ -2299,9 +2194,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-nt-mappings"
-></A
-><B
+NAME="faq-nt-mappings"><B
 >A.6.3. </B
 >
 	    CGI's are failing with a "something.cgi is not a valid Windows NT
@ -2322,9 +2215,7 @@ CLASS="answer"
 ><P
 >&#13;	    Microsoft has some advice on this matter, as well:
 	    <A
-NAME="AEN2114"
-></A
-><BLOCKQUOTE
+NAME="AEN2148"><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
 ><P
 >&#13;		"Set application mappings. In the ISM, map the extension for the script
@ -2347,9 +2238,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-nt-dbi"
-></A
-><B
+NAME="faq-nt-dbi"><B
 >A.6.4. </B
 >
 	    I'm having trouble with the perl modules for NT not being able to talk to
@ -2415,18 +2304,14 @@ TARGET="_top"
 CLASS="qandadiv"
 ><H3
 ><A
-NAME="faq-use"
-></A
->7. Bugzilla Usage</H3
+NAME="faq-use">7. Bugzilla Usage</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-use-changeaddress"
-></A
-><B
+NAME="faq-use-changeaddress"><B
 >A.7.1. </B
 >
 	    How do I change my user name (email address) in Bugzilla?
@ -2449,9 +2334,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-use-query"
-></A
-><B
+NAME="faq-use-query"><B
 >A.7.2. </B
 >
 	    The query page is very confusing. Isn't there a simpler way to query?
@ -2475,9 +2358,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-use-accept"
-></A
-><B
+NAME="faq-use-accept"><B
 >A.7.3. </B
 >
 	    I'm confused by the behavior of the "accept" button in the Show Bug form.
@ -2529,9 +2410,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-use-attachment"
-></A
-><B
+NAME="faq-use-attachment"><B
 >A.7.4. </B
 >
 	    I can't upload anything into the database via the "Create Attachment"
@ -2556,9 +2435,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-use-keyword"
-></A
-><B
+NAME="faq-use-keyword"><B
 >A.7.5. </B
 >
 	    How do I change a keyword in Bugzilla, once some bugs are using it?
@ -2576,23 +2453,54 @@ CLASS="answer"
 	  </P
 ></DIV
 ></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-hacking"
-></A
->8. Bugzilla Hacking</H3
 ><DIV
 CLASS="qandaentry"
 ><DIV
 CLASS="question"
 ><P
 ><A
-NAME="faq-hacking-templatestyle"
-></A
+NAME="faq-use-close"><B
+>A.7.6. </B
+>
+        Why can't I close bugs from the "Change Several Bugs at Once" page?
+      </P
+></DIV
+><DIV
+CLASS="answer"
+><P
 ><B
+> </B
+>
+        The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
+        You <EM
+>can</EM
+> mass-CLOSE bugs from the change several
+        bugs at once page. <EM
+>but</EM
+>, every bug listed on the
+        page has to be in VERIFIED state before the control to do it will show
+        up on the form. You can also mass-VERIFY, but every bug listed has to be
+        RESOLVED in order for the control to show up on the form. The logic
+        behind this is that if you pick one of the bugs that's not VERIFIED and
+        try to CLOSE it, the bug change will fail miserably (thus killing any
+        changes in the list after it while doing the bulk change) so it doesn't
+        even give you the choice.
+      </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="qandadiv"
+><H3
+><A
+NAME="faq-hacking">8. Bugzilla Hacking</H3
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-hacking-templatestyle"><B
 >A.8.1. </B
 >
 	    What kind of style should I use for templatization?
@ -2649,9 +2557,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-hacking-bugzillabugs"
-></A
-><B
+NAME="faq-hacking-bugzillabugs"><B
 >A.8.2. </B
 >
 	    What bugs are in Bugzilla right now?
@ -2695,9 +2601,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-hacking-priority"
-></A
-><B
+NAME="faq-hacking-priority"><B
 >A.8.3. </B
 >
 	    How can I change the default priority to a null value?  For instance, have the default
@ -2726,9 +2630,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="faq-hacking-patches"
-></A
-><B
+NAME="faq-hacking-patches"><B
 >A.8.4. </B
 >
 	    What's the best way to submit patches?  What guidelines should I follow?
--- a/webtools/bugzilla/docs/html/gfdl-0.html
+++ b/webtools/bugzilla/docs/html/gfdl-0.html
@ -4,7 +4,8 @@
 >PREAMBLE</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-0"
-></A
->0. PREAMBLE</H1
+NAME="gfdl-0">0. PREAMBLE</H1
 ><P
 >The purpose of this License is to make a manual, textbook, or other
    written document "free" in the sense of freedom: to assure everyone the
--- a/webtools/bugzilla/docs/html/gfdl-1.html
+++ b/webtools/bugzilla/docs/html/gfdl-1.html
@ -4,7 +4,8 @@
 >APPLICABILITY AND DEFINITIONS</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-1"
-></A
->1. APPLICABILITY AND DEFINITIONS</H1
+NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H1
 ><P
 >This License applies to any manual or other work that contains a
    notice placed by the copyright holder saying it can be distributed under
--- a/webtools/bugzilla/docs/html/gfdl-10.html
+++ b/webtools/bugzilla/docs/html/gfdl-10.html
@ -4,7 +4,8 @@
 >FUTURE REVISIONS OF THIS LICENSE</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-10"
-></A
->10. FUTURE REVISIONS OF THIS LICENSE</H1
+NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H1
 ><P
 >The Free Software Foundation may publish new, revised versions of
    the GNU Free Documentation License from time to time. Such new versions
--- a/webtools/bugzilla/docs/html/gfdl-2.html
+++ b/webtools/bugzilla/docs/html/gfdl-2.html
@ -4,7 +4,8 @@
 >VERBATIM COPYING</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-2"
-></A
->2. VERBATIM COPYING</H1
+NAME="gfdl-2">2. VERBATIM COPYING</H1
 ><P
 >You may copy and distribute the Document in any medium, either
    commercially or noncommercially, provided that this License, the
--- a/webtools/bugzilla/docs/html/gfdl-3.html
+++ b/webtools/bugzilla/docs/html/gfdl-3.html
@ -4,7 +4,8 @@
 >COPYING IN QUANTITY</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-3"
-></A
->3. COPYING IN QUANTITY</H1
+NAME="gfdl-3">3. COPYING IN QUANTITY</H1
 ><P
 >If you publish printed copies of the Document numbering more than
    100, and the Document's license notice requires Cover Texts, you must
--- a/webtools/bugzilla/docs/html/gfdl-4.html
+++ b/webtools/bugzilla/docs/html/gfdl-4.html
@ -4,7 +4,8 @@
 >MODIFICATIONS</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-4"
-></A
->4. MODIFICATIONS</H1
+NAME="gfdl-4">4. MODIFICATIONS</H1
 ><P
 >You may copy and distribute a Modified Version of the Document
    under the conditions of sections 2 and 3 above, provided that you release
--- a/webtools/bugzilla/docs/html/gfdl-5.html
+++ b/webtools/bugzilla/docs/html/gfdl-5.html
@ -4,7 +4,8 @@
 >COMBINING DOCUMENTS</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-5"
-></A
->5. COMBINING DOCUMENTS</H1
+NAME="gfdl-5">5. COMBINING DOCUMENTS</H1
 ><P
 >You may combine the Document with other documents released under
    this License, under the terms defined in section 4 above for modified
--- a/webtools/bugzilla/docs/html/gfdl-6.html
+++ b/webtools/bugzilla/docs/html/gfdl-6.html
@ -4,7 +4,8 @@
 >COLLECTIONS OF DOCUMENTS</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-6"
-></A
->6. COLLECTIONS OF DOCUMENTS</H1
+NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H1
 ><P
 >You may make a collection consisting of the Document and other
    documents released under this License, and replace the individual copies
--- a/webtools/bugzilla/docs/html/gfdl-7.html
+++ b/webtools/bugzilla/docs/html/gfdl-7.html
@ -4,7 +4,8 @@
 >AGGREGATION WITH INDEPENDENT WORKS</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-7"
-></A
->7. AGGREGATION WITH INDEPENDENT WORKS</H1
+NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H1
 ><P
 >A compilation of the Document or its derivatives with other
    separate and independent documents or works, in or on a volume of a
--- a/webtools/bugzilla/docs/html/gfdl-8.html
+++ b/webtools/bugzilla/docs/html/gfdl-8.html
@ -4,7 +4,8 @@
 >TRANSLATION</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-8"
-></A
->8. TRANSLATION</H1
+NAME="gfdl-8">8. TRANSLATION</H1
 ><P
 >Translation is considered a kind of modification, so you may
    distribute translations of the Document under the terms of section 4.
--- a/webtools/bugzilla/docs/html/gfdl-9.html
+++ b/webtools/bugzilla/docs/html/gfdl-9.html
@ -4,7 +4,8 @@
 >TERMINATION</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-9"
-></A
->9. TERMINATION</H1
+NAME="gfdl-9">9. TERMINATION</H1
 ><P
 >You may not copy, modify, sublicense, or distribute the Document
    except as expressly provided for under this License. Any other attempt to
--- a/webtools/bugzilla/docs/html/gfdl-howto.html
+++ b/webtools/bugzilla/docs/html/gfdl-howto.html
@ -4,7 +4,8 @@
 >How to use this License for your documents</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,17 +73,13 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="gfdl-howto"
-></A
->How to use this License for your documents</H1
+NAME="gfdl-howto">How to use this License for your documents</H1
 ><P
 >To use this License in a document you have written, include a copy
    of the License in the document and put the following copyright and
    license notices just after the title page:</P
 ><A
-NAME="AEN2441"
-></A
-><BLOCKQUOTE
+NAME="AEN2482"><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
 ><P
 >Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
--- a/webtools/bugzilla/docs/html/gfdl.html
+++ b/webtools/bugzilla/docs/html/gfdl.html
@ -4,7 +4,8 @@
 >GNU Free Documentation License</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="appendix"
 ><H1
 ><A
-NAME="gfdl"
-></A
->Appendix E. GNU Free Documentation License</H1
+NAME="gfdl">Appendix E. GNU Free Documentation License</H1
 ><DIV
 CLASS="TOC"
 ><DL
@ -143,9 +142,7 @@ HREF="gfdl-howto.html"
 ><P
 >Version 1.1, March 2000</P
 ><A
-NAME="AEN2351"
-></A
-><BLOCKQUOTE
+NAME="AEN2392"><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
 ><P
 >Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
--- a/webtools/bugzilla/docs/html/glossary.html
+++ b/webtools/bugzilla/docs/html/glossary.html
@ -4,7 +4,8 @@
 >Glossary</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -61,17 +62,13 @@ WIDTH="100%"></DIV
 CLASS="GLOSSARY"
 ><H1
 ><A
-NAME="glossary"
-></A
->Glossary</H1
+NAME="glossary">Glossary</H1
 ><DIV
 CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="AEN2446"
-></A
->0-9, high ascii</H1
+NAME="AEN2487">0-9, high ascii</H1
 ><DL
 ><DT
 ><B
@ -103,15 +100,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-a"
-></A
->A</H1
+NAME="gloss-a">A</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-apache"
-></A
-><B
+NAME="gloss-apache"><B
 >Apache</B
 ></DT
 ><DD
@ -250,9 +243,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-b"
-></A
->B</H1
+NAME="gloss-b">B</H1
 ><DL
 ><DT
 ><B
@ -292,9 +283,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="gloss-bugzilla"
-></A
-><B
+NAME="gloss-bugzilla"><B
 >Bugzilla</B
 ></DT
 ><DD
@ -309,15 +298,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-c"
-></A
->C</H1
+NAME="gloss-c">C</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-cgi"
-></A
-><B
+NAME="gloss-cgi"><B
 >Common Gateway Interface</B
 ></DT
 > (CGI)<DD
@ -335,9 +320,7 @@ CLASS="acronym"
 ></DD
 ><DT
 ><A
-NAME="gloss-component"
-></A
-><B
+NAME="gloss-component"><B
 >Component</B
 ></DT
 ><DD
@ -349,9 +332,7 @@ NAME="gloss-component"
 ></DD
 ><DT
 ><A
-NAME="gloss-cpan"
-></A
-><B
+NAME="gloss-cpan"><B
 >Comprehensive Perl Archive Network</B
 ></DT
 > (CPAN)<DD
@ -376,9 +357,7 @@ CLASS="glossterm"
 ></DD
 ><DT
 ><A
-NAME="gloss-contrib"
-></A
-><B
+NAME="gloss-contrib"><B
 ><TT
 CLASS="filename"
 >contrib</TT
@ -437,9 +416,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-d"
-></A
->D</H1
+NAME="gloss-d">D</H1
 ><DL
 ><DT
 ><B
@ -468,15 +445,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-g"
-></A
->G</H1
+NAME="gloss-g">G</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-groups"
-></A
-><B
+NAME="gloss-groups"><B
 >Groups</B
 ></DT
 ><DD
@ -508,15 +481,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-j"
-></A
->J</H1
+NAME="gloss-j">J</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-javascript"
-></A
-><B
+NAME="gloss-javascript"><B
 >JavaScript</B
 ></DT
 ><DD
@ -531,15 +500,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-m"
-></A
->M</H1
+NAME="gloss-m">M</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-mta"
-></A
-><B
+NAME="gloss-mta"><B
 >Message Transport Agent</B
 ></DT
 > (MTA)<DD
@ -567,9 +532,7 @@ CLASS="literal"
 ></DD
 ><DT
 ><A
-NAME="gloss-mysql"
-></A
-><B
+NAME="gloss-mysql"><B
 >MySQL</B
 ></DT
 ><DD
@ -646,15 +609,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-p"
-></A
->P</H1
+NAME="gloss-p">P</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-ppm"
-></A
-><B
+NAME="gloss-ppm"><B
 >Perl Package Manager</B
 ></DT
 > (PPM)<DD
@ -702,9 +661,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-q"
-></A
->Q</H1
+NAME="gloss-q">Q</H1
 ><DL
 ><DT
 ><B
@ -747,15 +704,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-r"
-></A
->R</H1
+NAME="gloss-r">R</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-rdbms"
-></A
-><B
+NAME="gloss-rdbms"><B
 >Relational DataBase Managment System</B
 ></DT
 > (RDBMS)<DD
@ -766,9 +719,7 @@ NAME="gloss-rdbms"
 ></DD
 ><DT
 ><A
-NAME="gloss-regexp"
-></A
-><B
+NAME="gloss-regexp"><B
 >Regular Expression</B
 ></DT
 > (regexp)<DD
@ -788,9 +739,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-s"
-></A
->S</H1
+NAME="gloss-s">S</H1
 ><DL
 ><DT
 ><B
@ -867,15 +816,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-t"
-></A
->T</H1
+NAME="gloss-t">T</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-target-milestone"
-></A
-><B
+NAME="gloss-target-milestone"><B
 >Target Milestone</B
 ></DT
 ><DD
@ -895,9 +840,7 @@ CLASS="QUOTE"
 ></DD
 ><DT
 ><A
-NAME="gloss-tcl"
-></A
-><B
+NAME="gloss-tcl"><B
 >Tool Command Language</B
 ></DT
 > (TCL)<DD
@ -915,15 +858,11 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="gloss-z"
-></A
->Z</H1
+NAME="gloss-z">Z</H1
 ><DL
 ><DT
 ><A
-NAME="gloss-zarro"
-></A
-><B
+NAME="gloss-zarro"><B
 >Zarro Boogs Found</B
 ></DT
 ><DD
@ -933,9 +872,7 @@ NAME="gloss-zarro"
        Terry had the following to say:
        </P
 ><A
-NAME="AEN2681"
-></A
-><TABLE
+NAME="AEN2722"><TABLE
 BORDER="0"
 WIDTH="100%"
 CELLSPACING="0"
--- a/webtools/bugzilla/docs/html/groups.html
+++ b/webtools/bugzilla/docs/html/groups.html
@ -4,7 +4,8 @@
 >Groups and Group Security</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="groups"
-></A
->5.5. Groups and Group Security</H1
+NAME="groups">5.5. Groups and Group Security</H1
 ><P
 >Groups allow the administrator
    to isolate bugs or products that should only be seen by certain people.
--- a/webtools/bugzilla/docs/html/hintsandtips.html
+++ b/webtools/bugzilla/docs/html/hintsandtips.html
@ -4,7 +4,8 @@
 >Hints and Tips</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="hintsandtips"
-></A
->3.2. Hints and Tips</H1
+NAME="hintsandtips">3.2. Hints and Tips</H1
 ><P
 >This section distills some Bugzilla tips and best practices
    that have been developed.</P
@ -83,9 +82,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN371"
-></A
->3.2.1. Autolinkification</H2
+NAME="AEN405">3.2.1. Autolinkification</H2
 ><P
 >Bugzilla comments are plain text - so posting HTML will result
      in literal HTML tags rather than being interpreted by a browser.
@ -148,9 +145,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="quicksearch"
-></A
->3.2.2. Quicksearch</H2
+NAME="quicksearch">3.2.2. Quicksearch</H2
 ><P
 >Quicksearch is a single-text-box query tool which uses
      metacharacters to indicate what is to be searched. For example, typing
@ -181,9 +176,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="commenting"
-></A
->3.2.3. Comments</H2
+NAME="commenting">3.2.3. Comments</H2
 ><P
 >If you are changing the fields on a bug, only comment if
      either you have something pertinent to say, or Bugzilla requires it.
@ -205,9 +198,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="attachments"
-></A
->3.2.4. Attachments</H2
+NAME="attachments">3.2.4. Attachments</H2
 ><P
 >&#13;      Use attachments, rather than comments, for large chunks of ASCII data,
      such as trace, debugging output files, or log files. That way, it doesn't
@ -231,9 +222,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN400"
-></A
->3.2.5. Filing Bugs</H2
+NAME="AEN434">3.2.5. Filing Bugs</H2
 ><P
 >Try to make sure that everything said in the summary is also 
      said in the first comment. Summaries are often updated and this will
--- a/webtools/bugzilla/docs/html/how.html
+++ b/webtools/bugzilla/docs/html/how.html
@ -4,7 +4,8 @@
 >How do I use Bugzilla?</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="how"
-></A
->3.1. How do I use Bugzilla?</H1
+NAME="how">3.1. How do I use Bugzilla?</H1
 ><P
 >This section contains information for end-users of Bugzilla. 
    There is a Bugzilla test installation, called 
@ -93,9 +92,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="myaccount"
-></A
->3.1.1. Create a Bugzilla Account</H2
+NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
 ><P
 >If you want to use Bugzilla, first you need to create an account.
      Consult with the administrator responsible for your installation of
@ -163,9 +160,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="bug_page"
-></A
->3.1.2. Anatomy of a Bug</H2
+NAME="bug_page">3.1.2. Anatomy of a Bug</H2
 ><P
 >The core of Bugzilla is the screen which displays a particular
      bug. It's a good place to explain some Bugzilla concepts. 
@ -430,9 +425,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="query"
-></A
->3.1.3. Searching for Bugs</H2
+NAME="query">3.1.3. Searching for Bugs</H2
 ><P
 >The Bugzilla Search page is is the interface where you can find
      any bug report, comment, or patch currently in the Bugzilla system. You
@ -460,9 +453,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="list"
-></A
->3.1.4. Bug Lists</H2
+NAME="list">3.1.4. Bug Lists</H2
 ><P
 >If you run a search, a list of matching bugs will be returned.
      The default search is to return all open bugs on the system - don't try
@ -534,9 +525,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="bugreports"
-></A
->3.1.5. Filing Bugs</H2
+NAME="bugreports">3.1.5. Filing Bugs</H2
 ><P
 >Years of bug writing experience has been distilled for your
      reading pleasure into the 
@ -589,6 +578,156 @@ TARGET="_top"
 ></LI
 ></OL
 ></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="patchviewer">3.1.6. Patch Viewer</H2
+><P
+>Viewing and reviewing patches in Bugzilla is often difficult due to
+      lack of context, improper format and the inherent readability issues that
+      raw patches present.  Patch Viewer is an enhancement to Bugzilla designed
+      to fix that by offering increased context, linking to sections, and
+      integrating with Bonsai, LXR and CVS.</P
+><P
+>Patch viewer allows you to:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>View patches in color, with side-by-side view rather than trying
+        to interpret the contents of the patch.</TD
+></TR
+><TR
+><TD
+>See the difference between two patches.</TD
+></TR
+><TR
+><TD
+>Get more context in a patch.</TD
+></TR
+><TR
+><TD
+>Collapse and expand sections of a patch for easy
+        reading.</TD
+></TR
+><TR
+><TD
+>Link to a particular section of a patch for discussion or
+        review</TD
+></TR
+><TR
+><TD
+>Go to Bonsai or LXR to see more context, blame, and
+        cross-references for the part of the patch you are looking at</TD
+></TR
+><TR
+><TD
+>Create a rawtext unified format diff out of any patch, no
+        matter what format it came from</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_view">3.1.6.1. Viewing Patches in Patch Viewer</H3
+><P
+>The main way to view a patch in patch viewer is to click on the
+        "Diff" link next to a patch in the Attachments list on a bug. You may
+        also do this within the edit window by clicking the "View Attachment As
+        Diff" button in the Edit Attachment screen.</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_diff">3.1.6.2. Seeing the Difference Between Two Patches</H3
+><P
+>To see the difference between two patches, you must first view the
+        newer patch in Patch Viewer.  Then select the older patch from the
+        dropdown at the top of the page ("Differences between [dropdown] and
+        this patch") and click the "Diff" button. This will show you what
+        is new or changed in the newer patch.</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_context">3.1.6.3. Getting More Context in a Patch</H3
+><P
+>To get more context in a patch, you put a number in the textbox at
+        the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
+        This will give you that many lines of context before and after each
+        change. Alternatively, you can click on the "File" link there and it
+        will show each change in the full context of the file. This feature only
+        works against files that were diffed using "cvs diff".</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_collapse">3.1.6.4. Collapsing and Expanding Sections of a Patch</H3
+><P
+>To view only a certain set of files in a patch (for example, if a
+        patch is absolutely huge and you want to only review part of it at a
+        time), you can click the "(+)" and "(-)" links next to each file (to
+        expand it or collapse it). If you want to collapse all files or expand
+        all files, you can click the "Collapse All" and "Expand All" links at the
+        top of the page.</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_link">3.1.6.5. Linking to a Section of a Patch</H3
+><P
+>To link to a section of a patch (for example, if you want to be
+        able to give someone a URL to show them which part you are talking
+        about) you simply click the "Link Here" link on the section header. The
+        resulting URL can be copied and used in discussion. (Copy Link
+        Location in Mozilla works as well.)</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_bonsai_lxr">3.1.6.6. Going to Bonsai and LXR</H3
+><P
+>To go to Bonsai to get blame for the lines you are interested in,
+        you can click the "Lines XX-YY" link on the section header you are
+        interested in. This works even if the patch is against an old
+        version of the file, since Bonsai stores all versions of the file.</P
+><P
+>To go to LXR, you click on the filename on the file header
+        (unfortunately, since LXR only does the most recent version, line
+        numbers are likely to rot).</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="patchviewer_unified_diff">3.1.6.7. Creating a Unified Diff</H3
+><P
+>If the patch is not in a format that you like, you can turn it
+        into a unified diff format by clicking the "Raw Unified" link at the top
+        of the page.</P
+></DIV
+></DIV
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
--- a/webtools/bugzilla/docs/html/http.html
+++ b/webtools/bugzilla/docs/html/http.html
@ -4,7 +4,8 @@
 >HTTP Server Configuration</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="http"
-></A
->4.4. HTTP Server Configuration</H1
+NAME="http">4.4. HTTP Server Configuration</H1
 ><P
 >The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
    that can be configured to run <A
@ -100,9 +99,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="http-apache"
-></A
->4.4.1. Apache <SPAN
+NAME="http-apache">4.4.1. Apache <SPAN
 CLASS="productname"
 >httpd</SPAN
 ></H2
@ -236,9 +233,7 @@ CLASS="glossterm"
 ><DIV
 CLASS="example"
 ><A
-NAME="http-apache-htaccess"
-></A
-><P
+NAME="http-apache-htaccess"><P
 ><B
 >Example 4-2. <TT
 CLASS="filename"
@ -398,9 +393,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="http-iis"
-></A
->4.4.2. Microsoft <SPAN
+NAME="http-iis">4.4.2. Microsoft <SPAN
 CLASS="productname"
 >Internet Information Services</SPAN
 ></H2
@ -455,9 +448,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="http-aol"
-></A
->4.4.3. AOL Server</H2
+NAME="http-aol">4.4.3. AOL Server</H2
 ><P
 >Ben FrantzDale reported success using AOL Server with Bugzilla. He
      reported his experience and what appears below is based on that.
--- a/webtools/bugzilla/docs/html/index.html
+++ b/webtools/bugzilla/docs/html/index.html
@ -4,7 +4,8 @@
 >The Bugzilla Guide - 2.17.5 Development Release</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="NEXT"
 TITLE="About This Guide"
 HREF="about.html"><META
@ -36,28 +37,20 @@ ALINK="#0000FF"
 ><DIV
 CLASS="BOOK"
 ><A
-NAME="index"
-></A
-><DIV
+NAME="index"><DIV
 CLASS="TITLEPAGE"
 ><H1
 CLASS="title"
 ><A
-NAME="AEN2"
-></A
->The Bugzilla Guide - 2.17.5 Development Release</H1
+NAME="AEN2">The Bugzilla Guide - 2.17.5 Development Release</H1
 ><H3
 CLASS="author"
 ><A
-NAME="AEN5"
-></A
->Matthew P. Barnson</H3
+NAME="AEN5">Matthew P. Barnson</H3
 ><H3
 CLASS="author"
 ><A
-NAME="AEN9"
-></A
->Jacob Steenhagen</H3
+NAME="AEN9">Jacob Steenhagen</H3
 ><H3
 CLASS="corpauthor"
 >The Bugzilla Team</H3
@ -68,9 +61,7 @@ CLASS="pubdate"
 ><DIV
 CLASS="abstract"
 ><A
-NAME="AEN14"
-></A
-><P
+NAME="AEN14"><P
 ></P
 ><P
 >&#13;	      This is the documentation for Bugzilla, the mozilla.org
--- a/webtools/bugzilla/docs/html/installation.html
+++ b/webtools/bugzilla/docs/html/installation.html
@ -4,7 +4,8 @@
 >Installation</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="chapter"
 ><H1
 ><A
-NAME="installation"
-></A
->Chapter 4. Installation</H1
+NAME="installation">Chapter 4. Installation</H1
 ><DIV
 CLASS="TOC"
 ><DL
@ -117,7 +116,7 @@ HREF="stepbystep.html#install-setupdatabase"
 ></DT
 ><DT
 >4.1.7. <A
-HREF="stepbystep.html#AEN759"
+HREF="stepbystep.html#AEN793"
 ><TT
 CLASS="filename"
 >checksetup.pl</TT
@ -125,7 +124,7 @@ CLASS="filename"
 ></DT
 ><DT
 >4.1.8. <A
-HREF="stepbystep.html#AEN790"
+HREF="stepbystep.html#AEN824"
 >Configuring Bugzilla</A
 ></DT
 ></DL
@ -139,17 +138,17 @@ HREF="extraconfig.html"
 ><DL
 ><DT
 >4.2.1. <A
-HREF="extraconfig.html#AEN796"
+HREF="extraconfig.html#AEN830"
 >Dependency Charts</A
 ></DT
 ><DT
 >4.2.2. <A
-HREF="extraconfig.html#AEN811"
+HREF="extraconfig.html#AEN845"
 >Bug Graphs</A
 ></DT
 ><DT
 >4.2.3. <A
-HREF="extraconfig.html#AEN824"
+HREF="extraconfig.html#AEN858"
 >The Whining Cron</A
 ></DT
 ><DT
@ -257,12 +256,12 @@ HREF="troubleshooting.html"
 ><DL
 ><DT
 >4.5.1. <A
-HREF="troubleshooting.html#AEN1121"
+HREF="troubleshooting.html#AEN1155"
 >Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
 ></DT
 ><DT
 >4.5.2. <A
-HREF="troubleshooting.html#AEN1126"
+HREF="troubleshooting.html#AEN1160"
 >DBD::Sponge::db prepare failed</A
 ></DT
 ><DT
--- a/webtools/bugzilla/docs/html/integration.html
+++ b/webtools/bugzilla/docs/html/integration.html
@ -4,7 +4,8 @@
 >Integrating Bugzilla with Third-Party Tools</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,17 +73,13 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="integration"
-></A
->5.10. Integrating Bugzilla with Third-Party Tools</H1
+NAME="integration">5.10. Integrating Bugzilla with Third-Party Tools</H1
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="bonsai"
-></A
->5.10.1. Bonsai</H2
+NAME="bonsai">5.10.1. Bonsai</H2
 ><P
 >Bonsai is a web-based tool for managing 
    <A
@ -106,9 +103,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="cvs"
-></A
->5.10.2. CVS</H2
+NAME="cvs">5.10.2. CVS</H2
 ><P
 >CVS integration is best accomplished, at this point, using the
    Bugzilla Email Gateway.</P
@ -142,9 +137,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="scm"
-></A
->5.10.3. Perforce SCM</H2
+NAME="scm">5.10.3. Perforce SCM</H2
 ><P
 >You can find the project page for Bugzilla and Teamtrack Perforce
    integration (p4dti) at: 
@ -182,9 +175,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="tinderbox"
-></A
->5.10.4. Tinderbox/Tinderbox2</H2
+NAME="tinderbox">5.10.4. Tinderbox/Tinderbox2</H2
 ><P
 >We need Tinderbox integration information.</P
 ></DIV
--- a/webtools/bugzilla/docs/html/introduction.html
+++ b/webtools/bugzilla/docs/html/introduction.html
@ -4,7 +4,8 @@
 >Introduction</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="chapter"
 ><H1
 ><A
-NAME="introduction"
-></A
->Chapter 2. Introduction</H1
+NAME="introduction">Chapter 2. Introduction</H1
 ><DIV
 CLASS="TOC"
 ><DL
--- a/webtools/bugzilla/docs/html/newversions.html
+++ b/webtools/bugzilla/docs/html/newversions.html
@ -4,7 +4,8 @@
 >New Versions</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="newversions"
-></A
->1.3. New Versions</H1
+NAME="newversions">1.3. New Versions</H1
 ><P
 >&#13;      This is the 2.17.5 version of The Bugzilla Guide. It is so named 
      to match the current version of Bugzilla. 
--- a/webtools/bugzilla/docs/html/os-specific.html
+++ b/webtools/bugzilla/docs/html/os-specific.html
@ -4,7 +4,8 @@
 >OS Specific Installation Notes</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="os-specific"
-></A
->4.3. OS Specific Installation Notes</H1
+NAME="os-specific">4.3. OS Specific Installation Notes</H1
 ><P
 >Many aspects of the Bugzilla installation can be affected by the
    the operating system you choose to install it on. Sometimes it can be made
@ -95,9 +94,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="os-win32"
-></A
->4.3.1. Microsoft Windows</H2
+NAME="os-win32">4.3.1. Microsoft Windows</H2
 ><P
 >Making Bugzilla work on windows is still a very painful processes.
      The Bugzilla Team is working to make it easier, but that goal is not
@ -121,9 +118,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="win32-perl"
-></A
->4.3.1.1. Win32 Perl</H3
+NAME="win32-perl">4.3.1.1. Win32 Perl</H3
 ><P
 >Perl for Windows can be obtained from <A
 HREF="http://www.activestate.com/"
@ -142,9 +137,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="win32-perlmodules"
-></A
->4.3.1.2. Perl Modules on Win32</H3
+NAME="win32-perlmodules">4.3.1.2. Perl Modules on Win32</H3
 ><P
 >Bugzilla on Windows requires the same perl modules found in
        <A
@ -254,9 +247,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="win32-code-changes"
-></A
->4.3.1.3. Code changes required to run on win32</H3
+NAME="win32-code-changes">4.3.1.3. Code changes required to run on win32</H3
 ><P
 >Unfortunately, Bugzilla still doesn't run "out of the box" on
        Windows.  There is work in progress to make this easier, but until that
@ -274,9 +265,7 @@ CLASS="section"
 ><H4
 CLASS="section"
 ><A
-NAME="win32-code-checksetup"
-></A
->4.3.1.3.1. Changes to <TT
+NAME="win32-code-checksetup">4.3.1.3.1. Changes to <TT
 CLASS="filename"
 >checksetup.pl</TT
 ></H4
@ -361,9 +350,7 @@ CLASS="section"
 ><H4
 CLASS="section"
 ><A
-NAME="win32-code-bugmail"
-></A
->4.3.1.3.2. Changes to <TT
+NAME="win32-code-bugmail">4.3.1.3.2. Changes to <TT
 CLASS="filename"
 >BugMail.pm</TT
 ></H4
@ -442,9 +429,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="win32-http"
-></A
->4.3.1.4. Serving the web pages</H3
+NAME="win32-http">4.3.1.4. Serving the web pages</H3
 ><P
 >As is the case on Unix based systems, any web server should be
        able to handle Bugzilla; however, the Bugzilla Team still recommends
@ -503,9 +488,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="os-macosx"
-></A
->4.3.2. <SPAN
+NAME="os-macosx">4.3.2. <SPAN
 CLASS="productname"
 >Mac OS X</SPAN
 ></H2
@ -697,9 +680,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="os-mandrake"
-></A
->4.3.3. Linux-Mandrake 8.0</H2
+NAME="os-mandrake">4.3.3. Linux-Mandrake 8.0</H2
 ><P
 >Linux-Mandrake 8.0 includes every required and optional library
      for Bugzilla. The easiest way to install them is by using the
--- a/webtools/bugzilla/docs/html/parameters.html
+++ b/webtools/bugzilla/docs/html/parameters.html
@ -4,7 +4,8 @@
 >Bugzilla Configuration</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="parameters"
-></A
->5.1. Bugzilla Configuration</H1
+NAME="parameters">5.1. Bugzilla Configuration</H1
 ><P
 >Bugzilla is configured by changing various parameters, accessed
    from the "Edit parameters" link in the page footer. Here are
--- a/webtools/bugzilla/docs/html/patches.html
+++ b/webtools/bugzilla/docs/html/patches.html
@ -4,7 +4,8 @@
 >Useful Patches and Utilities for Bugzilla</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -71,9 +72,7 @@ WIDTH="100%"></DIV
 CLASS="appendix"
 ><H1
 ><A
-NAME="patches"
-></A
->Appendix C. Useful Patches and Utilities for Bugzilla</H1
+NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
--- a/webtools/bugzilla/docs/html/programadmin.html
+++ b/webtools/bugzilla/docs/html/programadmin.html
@ -4,7 +4,8 @@
 >Product, Component, Milestone, and Version Administration</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,17 +73,13 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="programadmin"
-></A
->5.3. Product, Component, Milestone, and Version Administration</H1
+NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="products"
-></A
->5.3.1. Products</H2
+NAME="products">5.3.1. Products</H2
 ><P
 >&#13;      <A
 HREF="glossary.html#gloss-product"
@ -136,9 +133,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="components"
-></A
->5.3.2. Components</H2
+NAME="components">5.3.2. Components</H2
 ><P
 >Components are subsections of a Product. E.g. the computer game 
      you are designing may have a "UI"
@ -191,9 +186,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="versions"
-></A
->5.3.3. Versions</H2
+NAME="versions">5.3.3. Versions</H2
 ><P
 >Versions are the revisions of the product, such as "Flinders
      3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
@ -227,9 +220,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="milestones"
-></A
->5.3.4. Milestones</H2
+NAME="milestones">5.3.4. Milestones</H2
 ><P
 >Milestones are "targets" that you plan to get a bug fixed by. For
      example, you have a bug that you plan to fix for your 3.0 release, it
--- a/webtools/bugzilla/docs/html/rewrite.html
+++ b/webtools/bugzilla/docs/html/rewrite.html
@ -7,7 +7,8 @@
    magic</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -75,9 +76,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="rewrite"
-></A
->C.1. Apache 
+NAME="rewrite">C.1. Apache 
    <TT
 CLASS="filename"
 >mod_rewrite</TT
--- a/webtools/bugzilla/docs/html/security.html
+++ b/webtools/bugzilla/docs/html/security.html
@ -4,7 +4,8 @@
 >Bugzilla Security</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="security"
-></A
->5.6. Bugzilla Security</H1
+NAME="security">5.6. Bugzilla Security</H1
 ><DIV
 CLASS="warning"
 ><P
@ -173,9 +172,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="security-networking"
-></A
->5.6.1. TCP/IP Ports</H2
+NAME="security-networking">5.6.1. TCP/IP Ports</H2
 ><P
 >TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
      only needs 1... 2 if you need to use features that require e-mail such
@ -191,9 +188,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="security-mysql"
-></A
->5.6.2. MySQL</H2
+NAME="security-mysql">5.6.2. MySQL</H2
 ><P
 >MySQL ships by default with many settings that should be changed.
      By defaults it allows anybody to connect from localhost without a
@ -320,9 +315,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="security-daemon"
-></A
->5.6.3. Daemon Accounts</H2
+NAME="security-daemon">5.6.3. Daemon Accounts</H2
 ><P
 >Many daemons, such as Apache's httpd and MySQL's mysqld default to
      running as either <SPAN
@ -395,9 +388,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="security-access"
-></A
->5.6.4. Web Server Access Controls</H2
+NAME="security-access">5.6.4. Web Server Access Controls</H2
 ><P
 >There are many files that are placed in the Bugzilla directory
      area that should not be accessable from the web. Because of the way
--- a/webtools/bugzilla/docs/html/stepbystep.html
+++ b/webtools/bugzilla/docs/html/stepbystep.html
@ -4,7 +4,8 @@
 >Step-by-step Install</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="stepbystep"
-></A
->4.1. Step-by-step Install</H1
+NAME="stepbystep">4.1. Step-by-step Install</H1
 ><P
 >Bugzilla has been successfully installed under many different
      operating systems including almost all Unix clones and
@ -228,9 +227,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-mysql"
-></A
->4.1.1. MySQL</H2
+NAME="install-mysql">4.1.1. MySQL</H2
 ><P
 >Visit the MySQL homepage at 
      <A
@ -302,9 +299,7 @@ CLASS="filename"
 ><DIV
 CLASS="figure"
 ><A
-NAME="install-mysql-packets"
-></A
-><P
+NAME="install-mysql-packets"><P
 ><B
 >Figure 4-1. Set Max Packet Size in MySQL</B
 ></P
@ -344,9 +339,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-perl"
-></A
->4.1.2. Perl</H2
+NAME="install-perl">4.1.2. Perl</H2
 ><P
 >Any machine that doesn't have Perl on it is a sad machine indeed.
      Perl can be got in source form from <A
@ -366,9 +359,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-perlmodules"
-></A
->4.1.3. Perl Modules</H2
+NAME="install-perlmodules">4.1.3. Perl Modules</H2
 ><P
 >Perl modules can be found using
      <A
@ -402,9 +393,7 @@ HREF="os-specific.html#win32-perlmodules"
 ><DIV
 CLASS="example"
 ><A
-NAME="install-perlmodules-cpan"
-></A
-><P
+NAME="install-perlmodules-cpan"><P
 ><B
 >Example 4-1. Installing perl modules with CPAN</B
 ></P
@ -771,9 +760,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-bundle-bugzilla"
-></A
->4.1.3.1. Bundle::Bugzilla</H3
+NAME="install-modules-bundle-bugzilla">4.1.3.1. Bundle::Bugzilla</H3
 ><P
 >If you are running at least perl 5.6.1, you can save yourself a lot
      of time by using Bundle::Bugzilla. This bundle contains every module
@ -850,9 +837,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-appconfig"
-></A
->4.1.3.2. AppConfig (1.52)</H3
+NAME="install-modules-appconfig">4.1.3.2. AppConfig (1.52)</H3
 ><P
 >Dependency for Template Toolkit. We probably don't need to
      specifically check for it anymore.
@ -863,9 +848,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-cgi"
-></A
->4.1.3.3. CGI (2.88)</H3
+NAME="install-modules-cgi">4.1.3.3. CGI (2.88)</H3
 ><P
 >The CGI module parses form elements and cookies and does many
      other usefule things. It come as a part of recent perl distributions, but
@ -896,9 +879,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-data-dumper"
-></A
->4.1.3.4. Data::Dumper (any)</H3
+NAME="install-modules-data-dumper">4.1.3.4. Data::Dumper (any)</H3
 ><P
 >The Data::Dumper module provides data structure persistence for
      Perl (similar to Java's serialization). It comes with later
@ -930,9 +911,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-date-format"
-></A
->4.1.3.5. TimeDate modules (2.21)</H3
+NAME="install-modules-date-format">4.1.3.5. TimeDate modules (2.21)</H3
 ><P
 >Many of the more common date/time/calendar related Perl modules
      have been grouped into a bundle similar to the MySQL modules bundle.
@ -965,9 +944,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-dbi"
-></A
->4.1.3.6. DBI (1.32)</H3
+NAME="install-modules-dbi">4.1.3.6. DBI (1.32)</H3
 ><P
 >The DBI module is a generic Perl module used the
      MySQL-related modules. As long as your Perl installation was done
@ -999,9 +976,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-dbd-mysql"
-></A
->4.1.3.7. MySQL-related modules</H3
+NAME="install-modules-dbd-mysql">4.1.3.7. MySQL-related modules</H3
 ><P
 >The Perl/MySQL interface requires a few mutually-dependent Perl
      modules. These modules are grouped together into the the
@ -1044,9 +1019,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-file-spec"
-></A
->4.1.3.8. File::Spec (0.82)</H3
+NAME="install-file-spec">4.1.3.8. File::Spec (0.82)</H3
 ><P
 >File::Spec is a perl module that allows file operations, such as
      generating full path names, to work cross platform.
@ -1076,9 +1049,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-file-temp"
-></A
->4.1.3.9. File::Temp (any)</H3
+NAME="install-modules-file-temp">4.1.3.9. File::Temp (any)</H3
 ><P
 >File::Temp is used to generate a temporary filename that is
      guaranteed to be unique. It comes as a standard part of perl
@ -1108,9 +1079,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-template"
-></A
->4.1.3.10. Template Toolkit (2.08)</H3
+NAME="install-modules-template">4.1.3.10. Template Toolkit (2.08)</H3
 ><P
 >When you install Template Toolkit, you'll get asked various
      questions about features to enable. The defaults are fine, except
@ -1142,9 +1111,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-text-wrap"
-></A
->4.1.3.11. Text::Wrap (2001.0131)</H3
+NAME="install-modules-text-wrap">4.1.3.11. Text::Wrap (2001.0131)</H3
 ><P
 >Text::Wrap is designed to proved intelligent text wrapping.
      </P
@ -1168,9 +1135,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-gd"
-></A
->4.1.3.12. GD (1.20) [optional]</H3
+NAME="install-modules-gd">4.1.3.12. GD (1.20) [optional]</H3
 ><P
 >The GD library was written by Thomas Boutell a long while ago to
      programmatically generate images in C. Since then it's become the
@ -1278,9 +1243,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-chart-base"
-></A
->4.1.3.13. Chart::Base (0.99c) [optional]</H3
+NAME="install-modules-chart-base">4.1.3.13. Chart::Base (0.99c) [optional]</H3
 ><P
 >The Chart module provides Bugzilla with on-the-fly charting
      abilities. It can be installed in the usual fashion after it has been
@ -1307,9 +1270,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-xml-parser"
-></A
->4.1.3.14. XML::Parser (any) [Optional]</H3
+NAME="install-modules-xml-parser">4.1.3.14. XML::Parser (any) [Optional]</H3
 ><P
 >XML::Parser is used by the <TT
 CLASS="filename"
@ -1342,9 +1303,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-gd-graph"
-></A
->4.1.3.15. GD::Graph (any) [Optional]</H3
+NAME="install-modules-gd-graph">4.1.3.15. GD::Graph (any) [Optional]</H3
 ><P
 >In addition to GD listed above, the reporting interface of Bugzilla
      needs to have the GD::Graph module installed.
@ -1374,9 +1333,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-gd-text-align"
-></A
->4.1.3.16. GD::Text::Align (any) [Optional]</H3
+NAME="install-modules-gd-text-align">4.1.3.16. GD::Text::Align (any) [Optional]</H3
 ><P
 >GD::Text::Align, as the name implies, is used to draw aligned
      strings of text. It is needed by the reporting interface.
@ -1406,9 +1363,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-mime-parser"
-></A
->4.1.3.17. MIME::Parser (any) [Optional]</H3
+NAME="install-modules-mime-parser">4.1.3.17. MIME::Parser (any) [Optional]</H3
 ><P
 >MIME::Parser is only needed if you want to use the e-mail interface
      located in the <TT
@ -1441,9 +1396,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-patchreader"
-></A
->4.1.3.18. PatchReader (0.9.1) [Optional]</H3
+NAME="install-modules-patchreader">4.1.3.18. PatchReader (0.9.1) [Optional]</H3
 ><P
 >PatchReader is only needed if you want to use Patch Viewer, a
      Bugzilla feature to format patches in a pretty HTML fashion.  There are a
@ -1479,9 +1432,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-webserver"
-></A
->4.1.4. HTTP Server</H2
+NAME="install-webserver">4.1.4. HTTP Server</H2
 ><P
 >You have freedom of choice here, pretty much any web server that
      is capable of running <A
@ -1537,9 +1488,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-bzfiles"
-></A
->4.1.5. Bugzilla</H2
+NAME="install-bzfiles">4.1.5. Bugzilla</H2
 ><P
 >You should untar the Bugzilla files into a directory that you're
      willing to make writable by the default web server user (probably 
@ -1651,9 +1600,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-setupdatabase"
-></A
->4.1.6. Setting Up the MySQL Database</H2
+NAME="install-setupdatabase">4.1.6. Setting Up the MySQL Database</H2
 ><P
 >After you've gotten all the software installed and working you're
      ready to start preparing the database for its life as the back end to
@ -1808,9 +1755,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN759"
-></A
->4.1.7. <TT
+NAME="AEN793">4.1.7. <TT
 CLASS="filename"
 >checksetup.pl</TT
 ></H2
@ -1958,9 +1903,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN790"
-></A
->4.1.8. Configuring Bugzilla</H2
+NAME="AEN824">4.1.8. Configuring Bugzilla</H2
 ><P
 >&#13;      You should run through the parameters on the Edit Parameters page
      (link in the footer) and set them all to appropriate values. 
--- a/webtools/bugzilla/docs/html/troubleshooting.html
+++ b/webtools/bugzilla/docs/html/troubleshooting.html
@ -4,7 +4,8 @@
 >Troubleshooting</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="troubleshooting"
-></A
->4.5. Troubleshooting</H1
+NAME="troubleshooting">4.5. Troubleshooting</H1
 ><P
 >This section gives solutions to common Bugzilla installation
    problems.
@ -84,9 +83,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1121"
-></A
->4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
+NAME="AEN1155">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
 ><P
 >&#13;      Try executing <B
 CLASS="command"
@ -109,9 +106,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1126"
-></A
->4.5.2. DBD::Sponge::db prepare failed</H2
+NAME="AEN1160">4.5.2. DBD::Sponge::db prepare failed</H2
 ><P
 >&#13;        The following error message may appear due to a bug in DBD::mysql
        (over which the Bugzilla team have no control):
@ -195,9 +190,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="paranoid-security"
-></A
->4.5.3. cannot chdir(/var/spool/mqueue)</H2
+NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
 ><P
 >If you are installing Bugzilla on SuSE Linux, or some other
      distributions with 
@ -253,9 +246,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="trouble-filetemp"
-></A
->4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
+NAME="trouble-filetemp">4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
 ><P
 >This is caused by a bug in the version of
      <SPAN
@ -271,9 +262,7 @@ HREF="troubleshooting.html#trouble-filetemp-errors"
 ><DIV
 CLASS="figure"
 ><A
-NAME="trouble-filetemp-errors"
-></A
-><P
+NAME="trouble-filetemp-errors"><P
 ><B
 >Figure 4-2. Other File::Temp error messages</B
 ></P
@ -317,9 +306,7 @@ TARGET="_top"
 ><DIV
 CLASS="figure"
 ><A
-NAME="trouble-filetemp-patch"
-></A
-><P
+NAME="trouble-filetemp-patch"><P
 ><B
 >Figure 4-3. Patch for File::Temp in Perl 5.6.0</B
 ></P
--- a/webtools/bugzilla/docs/html/upgrading.html
+++ b/webtools/bugzilla/docs/html/upgrading.html
@ -4,7 +4,8 @@
 >Upgrading to New Releases</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="upgrading"
-></A
->5.9. Upgrading to New Releases</H1
+NAME="upgrading">5.9. Upgrading to New Releases</H1
 ><DIV
 CLASS="warning"
 ><P
@ -188,9 +187,7 @@ CLASS="filename"
 ><DIV
 CLASS="example"
 ><A
-NAME="upgrade-cvs"
-></A
-><P
+NAME="upgrade-cvs"><P
 ><B
 >Example 5-1. Upgrading using CVS</B
 ></P
@ -345,9 +342,7 @@ CLASS="command"
 ><DIV
 CLASS="example"
 ><A
-NAME="upgrade-tarball"
-></A
-><P
+NAME="upgrade-tarball"><P
 ><B
 >Example 5-2. Upgrading using the tarball</B
 ></P
@ -501,9 +496,7 @@ VALIGN="TOP"
 ><DIV
 CLASS="example"
 ><A
-NAME="upgrade-patches"
-></A
-><P
+NAME="upgrade-patches"><P
 ><B
 >Example 5-3. Upgrading using patches</B
 ></P
--- a/webtools/bugzilla/docs/html/useradmin.html
+++ b/webtools/bugzilla/docs/html/useradmin.html
@ -4,7 +4,8 @@
 >User Administration</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,17 +73,13 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="useradmin"
-></A
->5.2. User Administration</H1
+NAME="useradmin">5.2. User Administration</H1
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="defaultuser"
-></A
->5.2.1. Creating the Default User</H2
+NAME="defaultuser">5.2.1. Creating the Default User</H2
 ><P
 >When you first run checksetup.pl after installing Bugzilla, it
      will prompt you for the administrative username (email address) and
@ -125,17 +122,13 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="manageusers"
-></A
->5.2.2. Managing Other Users</H2
+NAME="manageusers">5.2.2. Managing Other Users</H2
 ><DIV
 CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="createnewusers"
-></A
->5.2.2.1. Creating new users</H3
+NAME="createnewusers">5.2.2.1. Creating new users</H3
 ><P
 >Your users can create their own user accounts by clicking the
        "New Account" link at the bottom of each page (assuming they
@ -206,9 +199,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="modifyusers"
-></A
->5.2.2.2. Modifying Users</H3
+NAME="modifyusers">5.2.2.2. Modifying Users</H3
 ><P
 >To see a specific user, search for their login name
        in the box provided on the "Edit Users" page. To see all users, 
--- a/webtools/bugzilla/docs/html/userpreferences.html
+++ b/webtools/bugzilla/docs/html/userpreferences.html
@ -4,7 +4,8 @@
 >User Preferences</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="userpreferences"
-></A
->3.3. User Preferences</H1
+NAME="userpreferences">3.3. User Preferences</H1
 ><P
 >Once you have logged in, you can customise various aspects of 
    Bugzilla via the "Edit prefs" link in the page footer.
@ -84,9 +83,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="accountsettings"
-></A
->3.3.1. Account Settings</H2
+NAME="accountsettings">3.3.1. Account Settings</H2
 ><P
 >On this tab, you can change your basic account information,
      including your password, email address and real name. For security
@ -109,9 +106,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="emailsettings"
-></A
->3.3.2. Email Settings</H2
+NAME="emailsettings">3.3.2. Email Settings</H2
 ><P
 >On this tab you can reduce or increase the amount of email sent
      you from Bugzilla, opting in our out depending on your relationship to
@ -158,9 +153,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="footersettings"
-></A
->3.3.3. Page Footer</H2
+NAME="footersettings">3.3.3. Page Footer</H2
 ><P
 >On the Search page, you can store queries in Bugzilla, so if you
      regularly run a particular query it is just a drop-down menu away. 
@ -172,9 +165,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="permissionsettings"
-></A
->3.3.4. Permissions</H2
+NAME="permissionsettings">3.3.4. Permissions</H2
 ><P
 >This is a purely informative page which outlines your current
      permissions on this installation of Bugzilla - what product groups you
--- a/webtools/bugzilla/docs/html/using.html
+++ b/webtools/bugzilla/docs/html/using.html
@ -4,7 +4,8 @@
 >Using Bugzilla</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="chapter"
 ><H1
 ><A
-NAME="using"
-></A
->Chapter 3. Using Bugzilla</H1
+NAME="using">Chapter 3. Using Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
@ -110,6 +109,11 @@ HREF="how.html#list"
 HREF="how.html#bugreports"
 >Filing Bugs</A
 ></DT
+><DT
+>3.1.6. <A
+HREF="how.html#patchviewer"
+>Patch Viewer</A
+></DT
 ></DL
 ></DD
 ><DT
@ -121,7 +125,7 @@ HREF="hintsandtips.html"
 ><DL
 ><DT
 >3.2.1. <A
-HREF="hintsandtips.html#AEN371"
+HREF="hintsandtips.html#AEN405"
 >Autolinkification</A
 ></DT
 ><DT
@ -141,7 +145,7 @@ HREF="hintsandtips.html#attachments"
 ></DT
 ><DT
 >3.2.5. <A
-HREF="hintsandtips.html#AEN400"
+HREF="hintsandtips.html#AEN434"
 >Filing Bugs</A
 ></DT
 ></DL
--- a/webtools/bugzilla/docs/html/variant-fenris.html
+++ b/webtools/bugzilla/docs/html/variant-fenris.html
@ -4,7 +4,8 @@
 >Loki Bugzilla (Fenris)</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-fenris"
-></A
->D.2. Loki Bugzilla (Fenris)</H1
+NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1
 ><P
 >Fenris was a fork from Bugzilla made by Loki Games; when
    Loki went into receivership, it died. While Loki's other code lives on,
--- a/webtools/bugzilla/docs/html/variant-issuezilla.html
+++ b/webtools/bugzilla/docs/html/variant-issuezilla.html
@ -4,7 +4,8 @@
 >Issuezilla</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-issuezilla"
-></A
->D.3. Issuezilla</H1
+NAME="variant-issuezilla">D.3. Issuezilla</H1
 ><P
 >Issuezilla was another fork from Bugzilla, made by collab.net and
    hosted at tigris.org. It is also dead; the primary focus of bug-tracking 
--- a/webtools/bugzilla/docs/html/variant-perforce.html
+++ b/webtools/bugzilla/docs/html/variant-perforce.html
@ -4,7 +4,8 @@
 >Perforce SCM</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-perforce"
-></A
->D.5. Perforce SCM</H1
+NAME="variant-perforce">D.5. Perforce SCM</H1
 ><P
 >Although Perforce isn't really a bug tracker, it can be used as
    such through the <SPAN
--- a/webtools/bugzilla/docs/html/variant-redhat.html
+++ b/webtools/bugzilla/docs/html/variant-redhat.html
@ -4,7 +4,8 @@
 >Red Hat Bugzilla</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-redhat"
-></A
->D.1. Red Hat Bugzilla</H1
+NAME="variant-redhat">D.1. Red Hat Bugzilla</H1
 ><P
 >Red Hat's old fork of Bugzilla which was based on version 2.8 is now
    obsolete. The newest version in use is based on version 2.17.1 and is in
--- a/webtools/bugzilla/docs/html/variant-scarab.html
+++ b/webtools/bugzilla/docs/html/variant-scarab.html
@ -4,7 +4,8 @@
 >Scarab</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-scarab"
-></A
->D.4. Scarab</H1
+NAME="variant-scarab">D.4. Scarab</H1
 ><P
 >Scarab is a new open source bug-tracking system built using Java
    Servlet technology. It is currently at version 1.0 beta 13.</P
--- a/webtools/bugzilla/docs/html/variant-sourceforge.html
+++ b/webtools/bugzilla/docs/html/variant-sourceforge.html
@ -4,7 +4,8 @@
 >SourceForge</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-sourceforge"
-></A
->D.6. SourceForge</H1
+NAME="variant-sourceforge">D.6. SourceForge</H1
 ><P
 >SourceForge is a way of coordinating geographically
    distributed free software and open source projects over the Internet.
--- a/webtools/bugzilla/docs/html/variants.html
+++ b/webtools/bugzilla/docs/html/variants.html
@ -4,7 +4,8 @@
 >Bugzilla Variants and Competitors</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -68,9 +69,7 @@ WIDTH="100%"></DIV
 CLASS="appendix"
 ><H1
 ><A
-NAME="variants"
-></A
->Appendix D. Bugzilla Variants and Competitors</H1
+NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
 ><DIV
 CLASS="TOC"
 ><DL
--- a/webtools/bugzilla/docs/html/voting.html
+++ b/webtools/bugzilla/docs/html/voting.html
@ -4,7 +4,8 @@
 >Voting</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="voting"
-></A
->5.4. Voting</H1
+NAME="voting">5.4. Voting</H1
 ><P
 >Voting allows users to be given a pot of votes which they can allocate
    to bugs, to indicate that they'd like them fixed. 
--- a/webtools/bugzilla/docs/html/whatis.html
+++ b/webtools/bugzilla/docs/html/whatis.html
@ -4,7 +4,8 @@
 >What is Bugzilla?</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="whatis"
-></A
->2.1. What is Bugzilla?</H1
+NAME="whatis">2.1. What is Bugzilla?</H1
 ><P
 >&#13;    Bugzilla is a bug- or issue-tracking system. Bug-tracking
    systems allow individual or groups of developers effectively to keep track
--- a/webtools/bugzilla/docs/html/why.html
+++ b/webtools/bugzilla/docs/html/why.html
@ -4,7 +4,8 @@
 >Why Should We Use Bugzilla?</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@ -72,9 +73,7 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="why"
-></A
->2.2. Why Should We Use Bugzilla?</H1
+NAME="why">2.2. Why Should We Use Bugzilla?</H1
 ><P
 >For many years, defect-tracking software has remained principally
    the domain of large software development houses. Even then, most shops
--- a/webtools/bugzilla/docs/pdf/Bugzilla-Guide.pdf
+++ b/webtools/bugzilla/docs/pdf/Bugzilla-Guide.pdf
--- a/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
+++ b/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt