Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and bug 26242.

The README is now gutted, pointers to Guide. Also some new sections added, old ones fixed, and notes appended to deprecated sections I've not yet had the heart to remove.

Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and bug 26242.
e5b9f4fa · barnboy%trilobyte.net · 7016a5a0 · e5b9f4fa · e5b9f4fa · e5b9f4fa
Commit e5b9f4fa authored Apr 04, 2008 by barnboy%trilobyte.net
7 changed files
--- a/docs/en/xml/Bugzilla-Guide.xml
+++ b/docs/en/xml/Bugzilla-Guide.xml
-<?xml version="1.0"?>
+<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
-                      "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
-    <!ENTITY % myents SYSTEM "bugzilla.ent">
-    %myents;
 <!-- Include macros -->
-<!ENTITY about SYSTEM "about.xml">
+<!ENTITY about SYSTEM "about.sgml">
-<!ENTITY conventions SYSTEM "conventions.xml">
+<!ENTITY conventions SYSTEM "conventions.sgml">
-<!ENTITY doc-index SYSTEM "index.xml">
+<!ENTITY doc-index SYSTEM "index.sgml">
-<!ENTITY gfdl SYSTEM "gfdl.xml">
+<!ENTITY faq SYSTEM "faq.sgml">
-<!ENTITY glossary SYSTEM "glossary.xml">
+<!ENTITY gfdl SYSTEM "gfdl.sgml">
-<!ENTITY installation SYSTEM "installation.xml">
+<!ENTITY glossary SYSTEM "glossary.sgml">
-<!ENTITY administration SYSTEM "administration.xml">
+<!ENTITY installation SYSTEM "installation.sgml">
-<!ENTITY security SYSTEM "security.xml">
+<!ENTITY administration SYSTEM "administration.sgml">
-<!ENTITY using SYSTEM "using.xml">
+<!ENTITY using SYSTEM "using.sgml">
-<!ENTITY integration SYSTEM "integration.xml">
+<!ENTITY integration SYSTEM "integration.sgml">
-<!ENTITY index SYSTEM "index.xml">
+<!ENTITY future SYSTEM "future.sgml">
-<!ENTITY customization SYSTEM "customization.xml">
+<!ENTITY index SYSTEM "index.sgml">
-<!ENTITY troubleshooting SYSTEM "troubleshooting.xml">
+<!ENTITY database SYSTEM "database.sgml">
-<!ENTITY patches SYSTEM "patches.xml">
+<!ENTITY patches SYSTEM "patches.sgml">
-<!ENTITY introduction SYSTEM "introduction.xml">
+<!ENTITY variants SYSTEM "variants.sgml">
-<!ENTITY modules SYSTEM "modules.xml">
+<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
-<!-- Things to change for a stable release:
-     * bz-ver to current stable
-     * bz-nexver to next stable
-     * bz-date to the release date
-     * landfillbase to the branch install
-     * Remove the BZ-DEVEL comments
-     - COMPILE DOCS AND CHECKIN -
-       Also, tag and tarball before completing
-     * bz-ver to devel version
-     For a devel release, simple bump bz-ver and bz-date
-->
-<!ENTITY bz-ver "3.1.3">
+]>
-<!ENTITY bz-nextver "3.2">
-<!ENTITY bz-date "2008-02-01">
-<!ENTITY current-year "2008">
-<!ENTITY landfillbase "http://landfill.bugzilla.org/bugzilla-tip/">
+<!-- Coding standards for this document 
-<!ENTITY bz "http://www.bugzilla.org/">
-<!ENTITY bzg-bugs "<ulink url='https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation'>Bugzilla Documentation</ulink>">
-<!ENTITY mysql "http://www.mysql.com/">
-<!ENTITY min-perl-ver "5.8.1">
+1.  Preface new or modified sections with a comment stating who
-]>
+ modified it and when; please also use the "authorinitials" tag.
+2.  There is no "two".
-<!-- Coding standards for this document 
+3.  Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
+4.  Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
+5.  Ensure all documents compile cleanly to HTML after modification.
+  The errors "DTD Declaration not allowed here" and "DTDDECL catalog types not supported"
+ are normal errors to be expected when compiling the whole guide.
+6.  Try to index important terms wherever possible.
+7.  Follow coding standards at http://www.linuxdoc.org.
+8.  All tags should be lowercase (needsfix)
-*  Other than the GFDL, please use the "section" tag instead of "sect1", 
+9.  Code being submitted for review should use the 
-   "sect2", etc.
+"review" tag. Documentation on this is available at 
-*  Use Entities to include files for new chapters in Bugzilla-Guide.xml.
+http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
-*  Try to use Entities for frequently-used passages of text as well.
+ under section 4.9.4, "Making notes on the text while it's being written".
-*  Ensure all documents compile cleanly to HTML after modification.
-   The warning, "DTDDECL catalog types not supported" is normal.
+10.  Please use sensible spacing.  The comments at the very end of each Guide
-*  Try to index important terms wherever possible.
-*  Use "glossterm" whenever you introduce a new term.
-*  Follow coding standards at http://www.tldp.org, and
-   check out the KDE guidelines (they are nice, too)
-   http://i18n.kde.org/doc/markup.html
-*  All tags should be lowercase.
-*  Please use sensible spacing.  The comments at the very end of each
 file define reasonable defaults for PSGML mode in EMACS.
-*  Double-indent tags, use double spacing whenever possible, and
+  Double-indent tags, use double spacing whenever possible,
-   try to avoid clutter and feel free to waste space in the code to make it 
+ try to avoid clutter and feel free to waste space in the code to make it more readable.
-   more readable.
 -->
-<book id="index">
+<BOOK ID="index">
 <!-- Header -->
-  <bookinfo>
+  <BOOKINFO>
-    <title>The Bugzilla Guide - &bz-ver; 
+    <TITLE>The Bugzilla Guide</TITLE>
-    <!-- BZ-DEVEL -->Development <!-- /BZ-DEVEL -->
+    <PUBDATE>v2.12.0, 24 April 2001</PUBDATE>
-    Release</title>
+    <AUTHOR>
+      <FIRSTNAME>Matthew</FIRSTNAME>
-    <authorgroup>
+      <OTHERNAME>P.</OTHERNAME>
-      <corpauthor>The Bugzilla Team</corpauthor>
+      <SURNAME>Barnson</SURNAME>
-    </authorgroup>
+      <affiliation>
+	<address><email>barnboy@trilobyte.net</email></address>
-    <pubdate>&bz-date;</pubdate>
+      </affiliation>
+    </AUTHOR>
-    <abstract>
-      <para>
+    <ABSTRACT>
-	      This is the documentation for Bugzilla, a 
+      <PARA>This is the documentation for Bugzilla, the Mozilla bug-tracking system.</PARA>
-	      bug-tracking system from mozilla.org.
+    </ABSTRACT>
-	      Bugzilla is an enterprise-class piece of software
-	      that tracks millions of bugs and issues for hundreds of
+    <REVHISTORY>
-	      organizations around the world.
+      <REVISION>
-      </para>
+	<REVNUMBER>v2.11</REVNUMBER>
+	<DATE>20 December 2000</DATE>
-      <para>
+	<AUTHORINITIALS>MPB</AUTHORINITIALS>
-        The most current version of this document can always be found on the
+	<REVREMARK>Converted the README, FAQ, and DATABASE information into SGML
-        <ulink url="http://www.bugzilla.org/docs/">Bugzilla 
+	  docbook format.</REVREMARK>
-        Documentation Page</ulink>.
+      </REVISION>
-      </para>
+      <revision>
-    </abstract>
+	<revnumber>2.11.1</revnumber>
+	<date>06 March 2001</date>
-    <keywordset>
+	<authorinitials>MPB</authorinitials>
-      <keyword>Bugzilla</keyword>
+	<revremark>
-      <keyword>Guide</keyword>
+	  Took way too long to revise this for 2.12 release.
-      <keyword>installation</keyword>
+	  Updated FAQ to use qandaset tags instead of literallayout,
-      <keyword>FAQ</keyword>
+	  cleaned up administration section, added User Guide section,
-      <keyword>administration</keyword>
+	  miscellaneous FAQ updates and third-party integration information.
-      <keyword>integration</keyword>
+	  From this point on all new tags are lowercase in preparation for the
-      <keyword>MySQL</keyword>
+	  2.13 release of the Guide in XML format instead of SGML.
-      <keyword>Mozilla</keyword>
+	</revremark>
-      <keyword>webtools</keyword>
+      </revision>
-    </keywordset>
-  </bookinfo>
+      <revision>
+	<revnumber>2.12.0</revnumber>
+	<date>24 April 2001</date>
+	<authorinitials>MPB</authorinitials>
+	<revremark>
+	  Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
+	  moving bugs from one keyword to another, clarified possible problems with the Landfill
+	  tutorial, fixed a boatload of typos and unclear sentence structures.  Incorporated the
+	  README into the UNIX installation section, and changed the README to indicate the deprecated
+	  status.  Things I know need work:  Used "simplelist" a lot, where I should have used
+	  "procedure" to tag things.  Need to lowercase all tags to be XML compliant.
+	</revremark>
+      </revision>
+    </REVHISTORY>
+    <KEYWORDSET>
+      <KEYWORD>Bugzilla</KEYWORD>
+      <KEYWORD>Guide</KEYWORD>
+      <KEYWORD>installation</KEYWORD>
+      <KEYWORD>FAQ</KEYWORD>
+      <KEYWORD>administration</KEYWORD>
+      <KEYWORD>integration</KEYWORD>
+      <KEYWORD>MySQL</KEYWORD>
+      <KEYWORD>Mozilla</KEYWORD>
+      <KEYWORD>webtools</KEYWORD>
+    </KEYWORDSET>
+  </BOOKINFO>
 <!-- About This Guide -->
 &about;
@@ -125,25 +133,31 @@
 <!-- Administering Bugzilla -->
 &administration;
-<!-- Securing Bugzilla -->
-&security;
 <!-- Using Bugzilla -->
 &using;
-<!-- Customizing Bugzilla -->
+<!-- Integrating Bugzilla with Third-Party Tools -->
-&customization;
+&integration;
+<!-- The Future of Bugzilla -->
+&future;
+<!-- Appendix: The Frequently Asked Questions -->
+&faq;
+<!-- Appendix: Required Bugzilla Software Links -->
+&requiredsoftware
-<!-- Appendix: Troubleshooting -->
+<!-- Appendix: The Database Schema -->
-&troubleshooting;
+&database;
+<!-- Appendix: Major Bugzilla Variants -->
+&variants;
 <!-- Appendix: Custom Patches -->
 &patches;
-<!-- Appendix: Manually Installing Perl Modules -->
+<!-- Appendix: The GNU Free Documentation License -->
-&modules;
-<!-- Appendix: GNU Free Documentation License -->
 &gfdl;
 <!-- Glossary -->
@@ -152,27 +166,31 @@
 <!-- Index -->
 &index;
+</BOOK>
-</book>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
-sgml-always-quote-attributes:t
+sgml-omittag:t
-sgml-auto-insert-required-elements:t
+sgml-shorttag:t
-sgml-balanced-tag-edit:t
+sgml-namecase-general:t
-sgml-exposed-tags:nil
 sgml-general-insert-case:lower
-sgml-indent-data:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
 sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
 sgml-local-catalogs:nil
 sgml-local-ecat-files:nil
-sgml-minimize-attributes:nil
-sgml-namecase-general:t
-sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
-sgml-shorttag:t
-sgml-tag-region-if-active:t
 End:
 -->
--- a/docs/en/xml/about.xml
+++ b/docs/en/xml/about.xml
-<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-<!ENTITY conventions SYSTEM "conventions.xml"> ] > -->
+<!ENTITY conventions SYSTEM "conventions.sgml"> ] >
-<!-- $Id: about.xml,v 1.1 2008/04/03 19:05:43 lpsolit%gmail.com Exp $ -->
+<CHAPTER ID="about">
-<chapter id="about">
+<TITLE>About This Guide</TITLE>
-<title>About This Guide</title>
+  <SECTION ID="aboutthisguide">
-  <section id="copyright">
+    <TITLE>Purpose and Scope of this Guide</TITLE>
-    <title>Copyright Information</title>
+    <PARA>
+      This document was started on September 17, 2000
-    <para>This document is copyright (c) 2000-&current-year; by the various
+      by Matthew P. Barnson after a great deal of procrastination updating the Bugzilla FAQ,
-    Bugzilla contributors who wrote it.</para>
+      which I left untouched for nearly half a year.
+      After numerous complete rewrites and reformatting, it is the document you see today.
-    <blockquote>
+    </PARA>
-      <para>
+    <PARA>
-	Permission is granted to copy, distribute and/or modify this
+      Despite the lack of updates, Bugzilla is simply the best piece of bug-tracking software
-	document under the terms of the GNU Free Documentation
+      the world has ever seen.  This document is intended to be the comprehensive guide to 
-	License, Version 1.1 or any later version published by the
+      the installation, administration, maintenance, and use of the Bugzilla bug-tracking system.
-	Free Software Foundation; with no Invariant Sections, no
+    </PARA>
-	Front-Cover Texts, and with no Back-Cover Texts. A copy of
+    <PARA>
-	the license is included in <xref linkend="gfdl"/>.
+      This release of the Bugzilla Guide is the <EMPHASIS>2.11</EMPHASIS> release.
-      </para>
+      It is so named that it may match the current version of Bugzilla.
-    </blockquote>
+      The numbering tradition stems from that used for many free software projects,
-    <para>
+      in which <EMPHASIS>even-numbered</EMPHASIS> point releases (1.2, 1.14, etc.)
-      If you have any questions regarding this document, its
+      are considered "stable releases", intended for public consumption; on the other 
-      copyright, or publishing this document in non-electronic form,
+      hand, <EMPHASIS>odd-numbered</EMPHASIS> point releases (1.3, 2.09, etc.)
-      please contact the Bugzilla Team. 
+      are considered unstable <EMPHASIS>development</EMPHASIS> releases intended
-    </para>
+      for advanced users, systems administrators, developers, and those who enjoy
-  </section>
+      a lot of pain. 
+    </PARA>
-  <section id="disclaimer">
+    <PARA>
-    <title>Disclaimer</title>
+      Newer revisions of the Bugzilla Guide will follow the numbering conventions of
-    <para>
+      the main-tree Bugzilla releases, available at
+      <ULINK URL="http://www.mozilla.org/bugs/source.html">Mozilla.org</ULINK>, with
+      the exception that intermediate releases will have a minor revision number
+      following a period.  For instance, if the current version of Bugzilla is 4.2,
+      the current "stable" version of the Bugzilla guide, in, say, it's fifth revision,
+      would be numbered "4.2.5".  Got it?  Good.
+    </PARA>
+    <PARA>
+      I wrote this in response to the enormous demand for decent Bugzilla documentation.
+      I have incorporated instructions from the Bugzilla README, Frequently Asked Questions,
+      Database Schema Document, and various mailing lists to create it.
+      Chances are, there are glaring errors in this documentation; please contact
+      <EMAIL>barnboy@trilobyte.net</EMAIL> to correct them.
+    </PARA>
+  </SECTION>
+  <SECTION ID="copyright">
+    <TITLE>Copyright Information</TITLE>
+    <BLOCKQUOTE>
+      <ATTRIBUTION>Copyright (c) 2000-2001 Matthew P. Barnson</ATTRIBUTION>
+      <PARA>
+	Permission is granted to copy, distribute and/or modify this document under thei
+	terms of the GNU Free Documentation License, Version 1.1 or any later version published 
+	by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and 
+	with no Back-Cover Texts.  A copy of the license is included in the section entitled 
+	"GNU Free Documentation LIcense".
+      </PARA>
+    </BLOCKQUOTE>
+    <PARA>
+      If you have any questions regarding this document, its' copyright, or publishing this
+      document in non-electronic form, please contact <EMAIL>barnboy@trilobyte.net</EMAIL>
+    </PARA>
+  </SECTION>
+  <SECTION ID="disclaimer">
+    <TITLE>Disclaimer</TITLE>
+    <PARA>
      No liability for the contents of this document can be accepted.
-      Follow the instructions herein at your own risk.
+      Use the concepts, examples, and other content at your own risk.
-      This document may contain errors
+      As this is a new edition of this document, there may be errors
-      and inaccuracies that may damage your system, cause your partner 
+      and inaccuracies that may damage your system.  Use of this document
-      to leave you, your boss to fire you, your cats to
+      may cause your girlfriend to leave you, your cats to pee on your
-      pee on your furniture and clothing, and global thermonuclear
+      furniture and clothing, your computer to cease functioning, your
-      war. Proceed with caution.
+      boss to fire you, and global thermonuclear war.  Proceed with caution.
-    </para>
+    </PARA>
-    <para>
+    <PARA>
-      Naming of particular products or brands should not be seen as
+      All copyrights are held by their respective owners, unless specifically
-      endorsements, with the exception of the term "GNU/Linux". We
+      noted otherwise.  Use of a term in this document should not be regarded
-      wholeheartedly endorse the use of GNU/Linux; it is an extremely 
+      as affecting the validity of any trademark or service mark.
-      versatile, stable,
+      In particular, I like to put down Microsoft(tm).  Live with it.
-      and robust operating system that offers an ideal operating
+    </PARA>
-      environment for Bugzilla.
+    <PARA>
-    </para>
+      Naming of particular products or brands should not be seen as endorsements,
-    <para>
+      with the exception of the term "GNU/Linux".
-      Although the Bugzilla development team has taken great care to
+      Use GNU/Linux.  Love it.  Bathe with it.  It is life and happiness.
-      ensure that all exploitable bugs have been fixed, security holes surely 
+      I endorse it wholeheartedly and encourage you to do the same.
-      exist in any piece of code. Great care should be taken both in 
+    </PARA>
-      the installation and usage of this software. The Bugzilla development
+    <PARA>
-      team members assume no liability for your use of Bugzilla. You have 
+      You are strongly recommended to make a backup of your system before
-      the source code, and are responsible for auditing it yourself to ensure
+      installing Bugzilla and at regular intervals thereafter.  Heaven knows
-      your security needs are met.
+      it's saved my bacon time after time; if you implement any suggestion in 
-    </para>
+      this Guide, implement this one!
-  </section>
+    </PARA>
+    <PARA>
+      Bugzilla has not undergone a complete security review.
+      Security holes probably exist in the code.
+      Great care should be taken both in the installation and usage of this software.
+      Carefully consider the implications of installing other network services with Bugzilla.
+    </PARA>
+  </SECTION>
 <!-- Section 2: New Versions -->
-  <section id="newversions">
+  <SECTION ID="newversions">
-    <title>New Versions</title>
+    <TITLE>New Versions</TITLE>
-    <para>
+    <PARA>
-      This is the &bz-ver; version of The Bugzilla Guide. It is so named 
+      This is the initial release of the Bugzilla Guide.
-      to match the current version of Bugzilla. 
+    </PARA>
-      <!-- BZ-DEVEL --> This version of the guide, like its associated Bugzilla version, is a
+    <PARA>
-      development version.<!-- /BZ-DEVEL --> 
+      This document can be found in the following places:
-    </para>
+    </PARA>
-    <para>
+    <PARA>
-      The latest version of this guide can always be found at <ulink
+      <ITEMIZEDLIST>
-      url="http://www.bugzilla.org"/>, or checked out via CVS by
+	<LISTITEM>
-      following the <ulink url="http://www.mozilla.org/cvs.html">Mozilla 
+	  <PARA>
-      CVS</ulink> instructions and check out the 
+	    <ULINK URL="http://www.trilobyte.net/barnsons/">TriloBYTE</ULINK>
-      <filename>mozilla/webtools/bugzilla/docs/</filename>
+	  </PARA>
-      subtree. However, you should read the version
+	</LISTITEM>
-      which came with the Bugzilla release you are using.
+	<LISTITEM>
-    </para>
+	  <PARA>
-    <para>
+	    <ULINK URL="http://www.mozilla.org/projects/bugzilla/">Mozilla.org</ULINK>
-      The Bugzilla Guide, or a section of it, is also available in
+	  </PARA>
-      the following languages:
+	</LISTITEM>
-      <ulink url="http://www.traduc.org/docs/guides/lecture/bugzilla/">French</ulink>,
+	<LISTITEM>
-      <ulink url="http://bugzilla-de.sourceforge.net/docs/html/">German</ulink>,
+	  <PARA>
-      <ulink url="http://www.bugzilla.jp/docs/2.18/">Japanese</ulink>.
+	    <ULINK URL="http://www.linuxdoc.org/">The Linux Documentation Project</ULINK>
-      Note that these may be outdated or not up to date.
+	  </PARA>
-    </para>
+	</LISTITEM>
+      </ITEMIZEDLIST>
-    <para>  
+    </PARA>
-      In addition, there are Bugzilla template localization projects in
+    <PARA>
-      the following languages. They may have translated documentation 
+      The latest version of this document can be checked out via CVS.
-      available: 
+      Please follow the instructions available at
-      <ulink url="http://sourceforge.net/projects/bugzilla-ar/">Arabic</ulink>,
+      <ULINK URL="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ULINK>,
-      <ulink url="http://sourceforge.net/projects/bugzilla-be/">Belarusian</ulink>,
+      and check out the mozilla/webtools/bugzilla/docs/ branch.
-      <ulink url="http://openfmi.net/projects/mozilla-bg/">Bulgarian</ulink>,
+    </PARA>
-      <ulink url="http://sourceforge.net/projects/bugzilla-br/">Brazilian Portuguese</ulink>,
+  </SECTION>
-      <ulink url="http://sourceforge.net/projects/bugzilla-cn/">Chinese</ulink>,
-      <ulink url="http://sourceforge.net/projects/bugzilla-fr/">French</ulink>,
+  <SECTION ID="credits">
-      <ulink url="http://germzilla.ganderbay.net/">German</ulink>,
+    <TITLE>Credits</TITLE>
-      <ulink url="http://sourceforge.net/projects/bugzilla-it/">Italian</ulink>,
+    <PARA>
-      <ulink url="http://www.bugzilla.jp/about/jp.html">Japanese</ulink>,
+      The people listed below have made enormous contributions to the creation
-      <ulink url="http://sourceforge.net/projects/bugzilla-kr/">Korean</ulink>,
+      of this Guide, through their dedicated hacking efforts,
-      <ulink url="http://sourceforge.net/projects/bugzilla-ru/">Russian</ulink> and
+      numerous e-mail and IRC support sessions,
-      <ulink url="http://sourceforge.net/projects/bugzilla-es/">Spanish</ulink>.
+      and overall excellent contribution to the Bugzilla community:
-    </para>
+    </PARA>
+    <PARA>
-    <para>  
+      <ULINK URL="mailto://terry@mozilla.org">Terry Weissman</ULINK>
-      If you would like to volunteer to translate the Guide into additional
+      for initially converting Bugzilla from BugSplat!
-      languages, please contact
+      and writing the README upon which this documentation is largely based.
-      <ulink url="mailto:justdave@bugzilla.org">Dave Miller</ulink>.
+    </PARA>
-    </para>
+    <PARA>
-  </section>
+      <ULINK URL="mailto://tara@tequilarista.org">Tara Hernandez</ULINK> 
+      for keeping Bugzilla development going strong after Terry left Mozilla.org
-  <section id="credits">
+    </PARA>
-    <title>Credits</title>
+    <PARA>
-    <para>
+      <ULINK URL="mailto://dkl@redhat.com">Dave Lawrence</ULINK>
-      The people listed below have made enormous contributions to the
+      for providing insight into the key differences between Red Hat's 
-      creation of this Guide, through their writing, dedicated hacking efforts,
+      customized Bugzilla, and being largely responsible for the
-      numerous e-mail and IRC support sessions, and overall excellent
+      "Red Hat Bugzilla" appendix
-      contribution to the Bugzilla community:
+    </PARA>
-    </para>
+    <PARA>
+      <ULINK URL="mailto://endico@mozilla.org">Dawn Endico</ULINK>
-    <!-- TODO: This is evil... there has to be a valid way to get this look -->
+      for being a hacker extraordinaire and putting up with my incessant
-    <variablelist>
+      questions and arguments on irc.mozilla.org in #mozwebtools
-      <varlistentry>
+    </PARA>
-        <term>Matthew P. Barnson <email>mbarnson@sisna.com</email></term>
+    <PARA>
-        <listitem>
+      Last but not least, all the members of the
-          <para>for the Herculean task of pulling together the Bugzilla Guide
+      <ULINK URL="news://news.mozilla.org/netscape/public/mozilla/webtools">
-          and shepherding it to 2.14.
+	netscape.public.mozilla.webtools</ULINK> newsgroup.  Without your
-          </para>
+      discussions, insight, suggestions, and patches, this could never have happened.
-        </listitem>
+    </PARA>
-      </varlistentry>
+  </SECTION>
+  <SECTION id="contributors">
-      <varlistentry>
+<TITLE>Contributors</TITLE>
-        <term>Terry Weissman <email>terry@mozilla.org</email></term>
+    <PARA>
-        <listitem>
+      Thanks go to these people for significant contributions
-          <para>for initially writing Bugzilla and creating the README upon
+      to this documentation (in no particular order):
-          which the UNIX installation documentation is largely based.
+    </PARA>
-          </para>
+    <PARA>
-        </listitem>
+      Zach Lipton (significant textual contributions),
-      </varlistentry>
+      Andrew Pearson,
+      Spencer Smith,
-      <varlistentry>
+      Eric Hanson,
-        <term>Tara Hernandez <email>tara@tequilarists.org</email></term>
+      Kevin Brannen,
-        <listitem>
+    </PARA>
-          <para>for keeping Bugzilla development going strong after Terry left
+  </SECTION>
-          mozilla.org and for running landfill.
+  <SECTION ID="feedback">
-          </para>
+    <TITLE>Feedback</TITLE>
-        </listitem>
+    <PARA>
-      </varlistentry>
+      I welcome feedback on this document.  Without your submissions and input,
+      this Guide cannot continue to exist.  Please mail additions, comments, criticisms, etc.
-      <varlistentry>
+      to <EMAIL>barnboy@trilobyte.net</EMAIL>.  Please send flames to 
-        <term>Dave Lawrence <email>dkl@redhat.com</email></term>
+      <EMAIL>devnull@localhost</EMAIL>
-        <listitem>
+    </PARA>
-          <para>for providing insight into the key differences between Red
+  </SECTION>
-          Hat's customized Bugzilla.
-          </para>
+  <SECTION ID="translations">
-        </listitem>
+    <TITLE>Translations</TITLE>
-      </varlistentry>
+    <PARA>
+      The Bugzilla Guide needs translators!
-      <varlistentry>
+      Please volunteer your translation into the language of your choice.
-        <term>Dawn Endico <email>endico@mozilla.org</email></term>
+      If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
-        <listitem>
+      <email>mozilla-webtools@mozilla.org</email>.  Since The Bugzilla Guide is also hosted on the
-          <para>for being a hacker extraordinaire and putting up with Matthew's
+      Linux Documentation Project, you would also do well to notify 
-          incessant questions and arguments on irc.mozilla.org in #mozwebtools
+    </PARA>
-          </para>
+  </SECTION>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>Jacob Steenhagen <email>jake@bugzilla.org</email></term>
-        <listitem>
-          <para>for taking over documentation during the 2.17 development
-          period.
-          </para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-	<term>Dave Miller <email>justdave@bugzilla.org</email></term>
-	<listitem>
-          <para>for taking over as project lead when Tara stepped down and
-	  continually pushing for the documentation to be the best it can be.
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-    <para>
-      Thanks also go to the following people for significant contributions 
-      to this documentation:
-      <simplelist type="inline">
-        <member>Kevin Brannen</member>
-        <member>Vlad Dascalu</member>
-        <member>Ben FrantzDale</member>
-        <member>Eric Hanson</member>
-        <member>Zach Lipton</member>
-        <member>Gervase Markham</member>
-        <member>Andrew Pearson</member>
-        <member>Joe Robins</member>
-        <member>Spencer Smith</member>
-        <member>Ron Teitelbaum</member>
-        <member>Shane Travis</member>
-        <member>Martin Wulffeld</member>
-      </simplelist>.
-    </para>
-    <para>
-      Also, thanks are due to the members of the 
-      <ulink url="news://news.mozilla.org/mozilla.support.bugzilla">
-      mozilla.support.bugzilla</ulink>
-      newsgroup (and its predecessor, netscape.public.mozilla.webtools).
-      Without your discussions, insight, suggestions, and patches,
-      this could never have happened.
-    </para>
-  </section>
  <!-- conventions used here (didn't want to give it a chapter of its own) -->
 &conventions;
- </chapter> 
+</CHAPTER>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:upper
+sgml-minimize-attributes:nil
 sgml-always-quote-attributes:t
-sgml-auto-insert-required-elements:t
-sgml-balanced-tag-edit:t
-sgml-exposed-tags:nil
-sgml-general-insert-case:lower
-sgml-indent-data:t 
 sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:Bugzilla-Guide\.sgml
+sgml-exposed-tags:nil
 sgml-local-catalogs:nil
 sgml-local-ecat-files:nil
-sgml-minimize-attributes:nil
+sgml-doctype:"<!DOCTYPE chapter PUBLIC \"-//OASIS//DTD DocBook V4.1//EN\">"
-sgml-namecase-general:t 
+End:
-sgml-omittag:t
+-->
-sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
-sgml-shorttag:t 
-sgml-tag-region-if-active:t 
-End: -->
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
--- a/docs/en/xml/installation.xml
+++ b/docs/en/xml/installation.xml
--- a/docs/en/xml/integration.xml
+++ b/docs/en/xml/integration.xml
-<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" >
 <!-- Keep these tools listings in alphabetical order please. -MPB -->
-<section id="integration">
+<chapter id="integration">
  <title>Integrating Bugzilla with Third-Party Tools</title>
-  <section id="bonsai"
+  <section id="bonsai">
-  xreflabel="Bonsai, the Mozilla automated CVS management system">
    <title>Bonsai</title>
+    <para>We need Bonsai integration information.</para>
-    <para>Bonsai is a web-based tool for managing 
-    <xref linkend="cvs" />
-    . Using Bonsai, administrators can control open/closed status of trees,
-    query a fast relational database back-end for change, branch, and comment
-    information, and view changes made since the last time the tree was
-    closed. Bonsai
-    also integrates with  
-    <xref linkend="tinderbox" />.
-    </para>
  </section>
-  <section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
+  <section id="cvs">
    <title>CVS</title>
+    <para>We need CVS integration information</para>
+  </section>
-    <para>CVS integration is best accomplished, at this point, using the
+  <section id="scm">
-    Bugzilla Email Gateway.</para>
+    <title>Perforce SCM</title>
+    <para>
-    <para>Follow the instructions in this Guide for enabling Bugzilla e-mail
+      Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
-    integration. Ensure that your check-in script sends an email to your
+      You can find the main project page at
-    Bugzilla e-mail gateway with the subject of 
+      <ulink url="http://www.ravenbrook.com/project/p4dti/">
-    <quote>[Bug XXXX]</quote>, 
+	http://www.ravenbrook.com/project/p4dti</ulink>.  "p4dti" is now an officially
-    and you can have CVS check-in comments append to your Bugzilla bug. If
+      supported product from Perforce, and you can find the "Perforce Public Depot"
-    you  want to have the bug be closed automatically, you'll have to modify
+      p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
-    the <filename>contrib/bugzilla_email_append.pl</filename> script.
+	http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
    </para>
+    <para>
-    <para>There is also a CVSZilla project, based upon somewhat dated 
+      Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless.  However,
-    Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to 
+      p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release.  I anticipate
-    email. Check it out at: <ulink url="http://www.cvszilla.org/"/>.
+      patches for 2.12 will be out shortly.  Check the project page regularly for updates, or
+      take the given patches and patch it manually.  p4dti is designed to support multiple defect
+      trackers, and maintains its own documentation for it.  Please consult the pages linked
+      above for further information.
    </para>
+    <para>
-    <para>Another system capable of CVS integration with Bugzilla is
+      Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
-    Scmbug. This system provides generic integration of Source code
+      to change the Bug ID to read (PRODUCT).bugID unless you hack it in.  Additionally, if you
-    Configuration Management with Bugtracking. Check it out at: <ulink
+      have synchronization problems, the easiest way to avoid them is to only put the bug
-    url="http://freshmeat.net/projects/scmbug/"/>.
+      information, comments, etc. into Bugzilla, and not into the Perforce change records.
+      They will link anyway; merely reference the bug ID fixed in your change description,
+      and put a comment into Bugzilla
+      giving the change ID that fixed the Bugzilla bug.  It's a process issue, not a technology
+      question.
    </para>
-  </section>
-  <section id="scm"
-  xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
-    <title>Perforce SCM</title>
-    <para>You can find the project page for Bugzilla and Teamtrack Perforce
-    integration (p4dti) at: 
-    <ulink url="http://www.ravenbrook.com/project/p4dti/"/>
-    . 
-    <quote>p4dti</quote>
-    is now an officially supported product from Perforce, and you can find
-    the "Perforce Public Depot" p4dti page at 
-    <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"/>
-    .</para>
-    <para>Integration of Perforce with Bugzilla, once patches are applied, is
-    seamless. Perforce replication information will appear below the comments
-    of each bug. Be certain you have a matching set of patches for the
-    Bugzilla version you are installing. p4dti is designed to support
-    multiple defect trackers, and maintains its own documentation for it.
-    Please consult the pages linked above for further information.</para>
  </section>
-  <section id="svn"
+  <section id="tinderbox">
-  xreflabel="Subversion, a compelling replacement for CVS">
+    <title>Tinderbox</title>
-     <title>Subversion</title>
+    <para>We need Tinderbox integration information</para>
-     <para>Subversion is a free/open-source version control system,
-     designed to overcome various limitations of CVS. Integration of
-     Subversion with Bugzilla is possible using Scmbug, a system
-     providing generic integration of Source Code Configuration
-     Management with Bugtracking. Scmbug is available at <ulink
-     url="http://freshmeat.net/projects/scmbug/"/>.</para>
  </section>
-  <section id="tinderbox"
+</chapter>
-  xreflabel="Tinderbox, the Mozilla automated build management system">
-    <title>Tinderbox/Tinderbox2</title>
-    <para>Tinderbox is a continuous-build system which can integrate with
-    Bugzilla - see
-    <ulink url="http://www.mozilla.org/projects/tinderbox"/> for details
-    of Tinderbox, and 
-    <ulink url="http://tinderbox.mozilla.org/showbuilds.cgi"/> to see it
-    in action.</para>
-  </section>
-</section>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
-sgml-always-quote-attributes:t
+sgml-omittag:t
-sgml-auto-insert-required-elements:t
+sgml-shorttag:t
-sgml-balanced-tag-edit:t
+sgml-namecase-general:t
-sgml-exposed-tags:nil
 sgml-general-insert-case:lower
-sgml-indent-data:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
 sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
 sgml-local-catalogs:nil
 sgml-local-ecat-files:nil
-sgml-minimize-attributes:nil
-sgml-namecase-general:t
-sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
-sgml-shorttag:t
-sgml-tag-region-if-active:t
 End:
 -->
--- a/docs/en/xml/patches.xml
+++ b/docs/en/xml/patches.xml
-<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
-<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
-  <title>Contrib</title>
+<appendix id="patches">
+  <title>Useful Patches and Utilities for Bugzilla</title>		
+<section id="setperl">
+    <title>The setperl.csh Utility</title>
    <para>	
-    There are a number of unofficial Bugzilla add-ons in the 
+      You can use the "setperl.csh" utility to quickly and easily
-    <filename class="directory">$BUGZILLA_ROOT/contrib/</filename>
+      change the path to perl on all your Bugzilla files.
-    directory. This section documents them.
+      This is a C-shell script; if you do not have "csh" or "tcsh" in the search
+      path on your system, it will not work!
    </para>	
+    <procedure>
-  <section id="cmdline">
+      <step>
-    <title>Command-line Search Interface</title>
 	<para>
-      There are a suite of Unix utilities for searching Bugzilla from the 
+	  Download the "setperl.csh" utility to your Bugzilla
-      command line. They live in the 
+	  directory and make it executable.
-      <filename class="directory">contrib/cmdline</filename> directory.
-      There are three files - <filename>query.conf</filename>,
-      <filename>buglist</filename> and <filename>bugs</filename>.
 	</para>
+	<substeps>
-    <warning>
+	  <step>
 	    <para>
-        These files pre-date the templatization work done as part of the
+	      <computeroutput>
-        2.16 release, and have not been updated.
+		<prompt>bash#</prompt>
+		<command>cd /your/path/to/bugzilla</command>
+	      </computeroutput>
 	    </para>
-    </warning>
+	  </step>
+	  <step>
 	  <para>
-      <filename>query.conf</filename> contains the mapping from
+	      <computeroutput>
-      options to field names and comparison types. Quoted option names
+		<prompt>bash#</prompt>
-      are <quote>grepped</quote> for, so it should be easy to edit this
+		<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
-      file. Comments (#) have no effect; you must make sure these lines
+	      </computeroutput>
-      do not contain any quoted <quote>option</quote>.
 	    </para>
+	  </step>
+	<step>
 	    <para>
-      <filename>buglist</filename> is a shell script that submits a
+	      <computeroutput>
-      Bugzilla query and writes the resulting HTML page to stdout.
+		<prompt>bash#</prompt>
-      It supports both short options, (such as <quote>-Afoo</quote>
+		<command>chmod u+x setperl.csh</command>
-      or <quote>-Rbar</quote>) and long options (such
+	      </computeroutput>
-      as <quote>--assignedto=foo</quote> or <quote>--reporter=bar</quote>).
-      If the first character of an option is not <quote>-</quote>, it is
-      treated as if it were prefixed with <quote>--default=</quote>.
 	    </para>
+	  </step>
+      </substeps>
+      </step>
+      <step>
 	<para>
-      The column list is taken from the COLUMNLIST environment variable.
+	  Prepare (and fix) Bugzilla file permissions.
-      This is equivalent to the <quote>Change Columns</quote> option
-      that is available when you list bugs in buglist.cgi. If you have
-      already used Bugzilla, grep for COLUMNLIST in your cookies file
-      to see your current COLUMNLIST setting.
 	</para>
+	<substeps>
+	  <step>
+	    <para>
+	      <computeroutput>
+		<prompt>bash#</prompt>
+		<command>chmod u+w *</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	  <step>
+	  <para>
+	      <computeroutput>
+		<prompt>bash#</prompt>
+		<command>chmod u+x duplicates.cgi</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	  <step>
+	    <para>
+	      <computeroutput>
+		<prompt>bash#</prompt>
+		<command>chmod a-x bug_status.html</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	</substeps>
+      </step>
+      <step>
+	<para>
+	  Run the script:
+	</para>
+	<para>
+	  <computeroutput>
+	    <prompt>bash#</prompt>
+	    <command>./setperl.csh /your/path/to/perl</command>
+	  </computeroutput>
+<example>
+	    <title>Using Setperl to set your perl path</title>
+	    <para>
+	      <computeroutput>
+	      <prompt>bash#</prompt>
+	      <command>./setperl.csh /usr/bin/perl</command>
+	      </computeroutput>
+            </para>
+	  </example>
+	</para>
+      </step>
+    </procedure>
+  </section>
+  <section id="cmdline">
+    <title>Command-line Bugzilla Queries</title>
+    <para>
+      Users can query Bugzilla from the command line using
+      this suite of utilities.
+    </para>
+    <para>
+      The query.conf file contains the mapping from options to field
+      names and comparison types.  Quoted option names are "grepped" for, so
+      it should be easy to edit this file.  Comments (#) have no effect; you
+      must make sure these lines do not contain any quoted "option"
+    </para>
+    <para>
+      buglist is a shell script which submits a Bugzilla query and writes the
+      resulting HTML page to stdout.  It supports both short options,
+      (such as "-Afoo" or "-Rbar") and long options (such as
+      "--assignedto=foo" or "--reporter=bar").  If the first character
+      of an option is not "-", it is treated as if it were prefixed
+      with "--default=".
+    </para>
+    <para>
+      The columlist is taken from the COLUMNLIST environment variable.
+      This is equivalent to the "Change Columns" option when you list
+      bugs in buglist.cgi.  If you have already used Bugzilla, use
+      <command>grep COLUMLIST ~/.netscape/cookies</command> to see
+      your current COLUMNLIST setting.
+    </para>
    <para>
-      <filename>bugs</filename> is a simple shell script which calls
+      bugs is a simple shell script which calls buglist and extracts
-      <filename>buglist</filename> and extracts the
+      the bug numbers from the output.  Adding the prefix
-      bug numbers from the output. Adding the prefix
+      "http://bugzilla.mozilla.org/buglist.cgi?bug_id="
-      <quote>http://bugzilla.mozilla.org/buglist.cgi?bug_id=</quote>
      turns the bug list into a working link if any bugs are found.
      Counting bugs is easy.  Pipe the results through
      <command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command>
    </para>
    <para>
-      Akkana Peck says she has good results piping 
+      Akkana says she has good results piping buglist output through
-      <filename>buglist</filename> output through 
      <command>w3m -T text/html -dump</command>
    </para>
+    <procedure>
+      <step>
+	<para>
+	  Download three files:
+	</para>
+	<substeps>
+	  <step>
+	    <para>
+	      <computeroutput>
+		<prompt>bash$</prompt>
+		<command>wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	  <step>
+	    <para>
+	      <computeroutput>
+		<prompt>bash$</prompt>
+		<command>wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	  <step>
+	    <para>
+	      <computeroutput>
+		<prompt>bash#</prompt>
+		<command>wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	</substeps>
+      </step>
+      <step>
+	<para>
+	  Make your utilities executable:
+	  <computeroutput>
+	    <prompt>bash$</prompt>
+	    <command>chmod u+x buglist bugs</command>
+	  </computeroutput>
+	</para>
+      </step>
+    </procedure>
  </section>
-  <section id="cmdline-bugmail">
+  <section id="quicksearch">
-    <title>Command-line 'Send Unsent Bug-mail' tool</title>
+    <title>The Quicksearch Utility</title>
    <para>
-      Within the <filename class="directory">contrib</filename> directory
+      Quicksearch is a new, experimental feature of the 2.12 release.
-      exists a utility with the descriptive (if compact) name
+      It consist of two Javascript files, "quicksearch.js" and "localconfig.js",
-      of <filename>sendunsentbugmail.pl</filename>. The purpose of this
+      and two documentation files, "quicksearch.html" and "quicksearchhack.html"
-      script is, simply, to send out any bug-related mail that should
-      have been sent by now, but for one reason or another has not.
    </para>
    <para>
-      To accomplish this task, <filename>sendunsentbugmail.pl</filename> uses
+      The index.html page has been updated to include the QuickSearch text box.
-      the same mechanism as the <filename>sanitycheck.cgi</filename> script;
-      it scans through the entire database looking for bugs with changes that
-      were made more than 30 minutes ago, but where there is no record of
-      anyone related to that bug having been sent mail. Having compiled a list,
-      it then uses the standard rules to determine who gets mail, and sends it
-      out.
    </para>
    <para>
-      As the script runs, it indicates the bug for which it is currently
+      To take full advantage of the query power, the Bugzilla maintainer must
-      sending mail; when it has finished, it gives a numerical count of how
+      edit "localconfig.js" according to the value sets used in the local installation.
-      many mails were sent and how many people were excluded. (Individual
+    </para>
-      user names are not recorded or displayed.) If the script produces
+    <para>
-      no output, that means no unsent mail was detected.
+      Currently, keywords must be hard-coded in localconfig.js.  If they are not,
+      keywords are not automatically recognized.  This means, if localconfig.js
+      is left unconfigured, that searching for a bug with the "foo" keyword
+      will only find bugs with "foo" in the summary, status whiteboard, product or
+      component name, but not those with the keyword "foo".
+    </para>
+    <para>
+      Workarounds for Bugzilla users:
+      <simplelist>
+	<member>search for '!foo' (this will find only bugs with the keyword "foo"</member>
+	<member>search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</member>
+      </simplelist>
    </para>
    <para>
-      <emphasis>Usage</emphasis>: move the sendunsentbugmail.pl script
+      When this tool is ported from client-side JavaScript to server-side Perl,
-      up into the main directory, ensure it has execute permission, and run it
+      the requirement for hard-coding keywords can be fixed.
-      from the command line (or from a cron job) with no parameters.
+      <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink>
+      has details.
    </para>
  </section>
 </appendix>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
-sgml-always-quote-attributes:t
+sgml-omittag:t
-sgml-auto-insert-required-elements:t
+sgml-shorttag:t
-sgml-balanced-tag-edit:t
+sgml-namecase-general:t
-sgml-exposed-tags:nil
 sgml-general-insert-case:lower
-sgml-indent-data:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
 sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
 sgml-local-catalogs:nil
 sgml-local-ecat-files:nil
-sgml-minimize-attributes:nil
-sgml-namecase-general:t
-sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
-sgml-shorttag:t
-sgml-tag-region-if-active:t
 End:
 -->
--- a/docs/en/xml/using.xml
+++ b/docs/en/xml/using.xml