1 files changed, 33 insertions, 14 deletions
diff --git a/docs/htmldocs/printingdebug.html b/docs/htmldocs/printingdebug.html
index 6b11f83727..acc81fdc00 100644
--- a/docs/htmldocs/printingdebug.html
+++ b/docs/htmldocs/printingdebug.html
@@ -5,11 +5,10 @@
 >Debugging Printing Problems</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
 REL="HOME"
 TITLE="SAMBA Project Documentation"
-HREF="Samba-HOWTO.html"><LINK
+HREF="samba-project-documentation.html"><LINK
 REL="PREVIOUS"
 TITLE="Printing Support in Samba 2.2.x"
 HREF="printing.html"><LINK
@@ -70,13 +69,17 @@ WIDTH="100%"></DIV
 CLASS="CHAPTER"
 ><H1
 ><A
-NAME="PRINTINGDEBUG">Chapter 8. Debugging Printing Problems</H1
+NAME="PRINTINGDEBUG"
+></A
+>Chapter 8. Debugging Printing Problems</H1
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1125">8.1. Introduction</H1
+NAME="AEN1128"
+></A
+>8.1. Introduction</H1
 ><P
 >This is a short description of how to debug printing problems with
 Samba. This describes how to debug problems with printing from a SMB
@@ -149,7 +152,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1141">8.2. Debugging printer problems</H1
+NAME="AEN1144"
+></A
+>8.2. Debugging printer problems</H1
 ><P
 >One way to debug printing problems is to start by replacing these
 command with shell scripts that record the arguments and the contents
@@ -204,7 +209,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1150">8.3. What printers do I have?</H1
+NAME="AEN1153"
+></A
+>8.3. What printers do I have?</H1
 ><P
 >You can use the 'testprns' program to check to see if the printer
 name you are using is recognized by Samba.  For example,  you can
@@ -231,7 +238,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1158">8.4. Setting up printcap and print servers</H1
+NAME="AEN1161"
+></A
+>8.4. Setting up printcap and print servers</H1
 ><P
 >You may need to set up some printcaps for your Samba system to use.
 It is strongly recommended that you use the facilities provided by
@@ -313,7 +322,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1186">8.5. Job sent, no output</H1
+NAME="AEN1189"
+></A
+>8.5. Job sent, no output</H1
 ><P
 >This is the most frustrating part of printing.  You may have sent the
 job,  verified that the job was forwarded,  set up a wrapper around
@@ -356,7 +367,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1197">8.6. Job sent, strange output</H1
+NAME="AEN1200"
+></A
+>8.6. Job sent, strange output</H1
 ><P
 >Once you have the job printing, you can then start worrying about
 making it print nicely.</P
@@ -400,7 +413,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1209">8.7. Raw PostScript printed</H1
+NAME="AEN1212"
+></A
+>8.7. Raw PostScript printed</H1
 ><P
 >This is a problem that is usually caused by either the print spooling
 system putting information at the start of the print job that makes
@@ -413,7 +428,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1212">8.8. Advanced Printing</H1
+NAME="AEN1215"
+></A
+>8.8. Advanced Printing</H1
 ><P
 >Note that you can do some pretty magic things by using your
 imagination with the "print command" option and some shell scripts.
@@ -427,7 +444,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1215">8.9. Real debugging</H1
+NAME="AEN1218"
+></A
+>8.9. Real debugging</H1
 ><P
 >If the above debug tips don't help, then maybe you need to bring in
 the bug guns, system tracing. See Tracing.txt in this directory.</P
@@ -458,7 +477,7 @@ WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="Samba-HOWTO.html"
+HREF="samba-project-documentation.html"
 ACCESSKEY="H"
 >Home</A
 ></TD