make DocBooks XML compatible

2004-12-31 22:14:29 +00:00
parent 124b6e62d7
commit 15ecb1acca
8 changed files with 18 additions and 15 deletions
@@ -20,7 +20,7 @@ This chapter will explain you the major steps and few gotchas of adding your own
 <para>How I Learned to Stop Worrying and Love the Configure Script</para>

 <para>
-It was decided pretty early in LCDproc's life to use GNU autoconf and GNU automake. This allows LCDproc to be ported to several platforms with much less effort. It can be quite daunting to understand how autoconf & automake interact with each others and with your code, but don't be discouraged. We have taken great care in making this as simple as possible for programers to add their own driver to LCDproc. Hopefully, you'll only have to modify two files, one for autoconf and one for automake.
+It was decided pretty early in LCDproc's life to use GNU autoconf and GNU automake. This allows LCDproc to be ported to several platforms with much less effort. It can be quite daunting to understand how autoconf &amp; automake interact with each others and with your code, but don't be discouraged. We have taken great care in making this as simple as possible for programers to add their own driver to LCDproc. Hopefully, you'll only have to modify two files, one for autoconf and one for automake.
 </para>

 <para>
@@ -1,4 +1,6 @@
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+<?xml version='1.0'?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN"
+                      "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd" [
  <!ENTITY bookinfo SYSTEM "bookinfo.docbook">
  <!ENTITY introduction SYSTEM "introduction.docbook">
  <!ENTITY shared-files SYSTEM "shared-files.docbook">
@@ -5,7 +5,7 @@
 <title>Configure LCDd</title>

 <para>
-As mentioned in the <link linkend=introduction>introduction</link>
+As mentioned in the <link linkend="introduction">introduction</link>
 LCDd, the LCDproc server, now (with version 0.4.3 of LCDproc) has its
 own configuration file, which is normally <filename>/etc/LCDd.conf</filename>.
 </para>
@@ -33,8 +33,8 @@ has a section which defines how the driver acts. Those sections start with
 [drivername].
 </para>
 <para>
-<anchor id=which-driver>The drivers are activated by specifiying them in a driver= line in the
-server section, like:
+<anchor id="which-driver">The drivers are activated by specifiying them in a driver= line in the
+server section, like:</anchor>
 </para>

 <example>
@@ -111,7 +111,7 @@ settings for the LCDproc server <application>LCDd</application>.
 <listitem>
 <para>
 Tells the server which driver(s) to use. See
-<link linkend=which-driver>above</link> for details
+<link linkend="which-driver">above</link> for details
 </para>
 <note>
 <para>
@@ -1029,7 +1029,7 @@ specifying which one (of multiple BWCT LCD devices) is wanted using the

 </sect2>

-<sect2 id=hd44780-compiling>
+<sect2 id="hd44780-compiling">
 <title>Compiling</title>

 <para>
@@ -82,9 +82,9 @@ settings for the lircin LCDproc driver.
 <term>lircrc=</term>
 <listitem>
 <para>
-<anchor id=which-lircrc>Normally all LIRC clients scan the file <filename>~/.lircrc</filename>.
+<anchor id="which-lircrc">Normally all LIRC clients scan the file <filename>~/.lircrc</filename>.
 However, you might want to have a separate file to configure the
-LCDproc lircin driver only.
+LCDproc lircin driver only.</anchor>
 </para>
 <para>
 This option enables you to specify the file you want the lircin
@@ -119,7 +119,7 @@ The prog=... line must be the same as in your <filename>~/.lircrc</filename>
 <para>
 As mentioned above you can either modify the <filename>~/.lircrc</filename>
 or use a separate file for the lircin LCDproc driver (See
-<link linkend=which-lircrc>above</link> for details).
+<link linkend="which-lircrc">above</link> for details).
 </para>

 <para>
@@ -88,8 +88,8 @@
 	  you have some idea of where you intend to permanently mount the module. For
 	  mounting ideas and tips, refer to the section "Mounting" below.
 	</para>
-	<Tip>
-	  <Title>Before you start</title>
+	<tip>
+	  <title>Before you start</title>
 	  <para>
 	    Your Matrix Orbital LCD or VFD module should be clearly marked with an
 	    indication of the module's power requirements. It should be either a 5 volt
@@ -18,7 +18,7 @@ debian tool), you can skip this this chapter.

 <para>
 If you're building this version from CVS, you'll need 
-autoconf, automake, aclocal & autoheader installed.
+autoconf, automake, aclocal &amp; autoheader installed.
 </para>

 <para>
@@ -1,5 +1,6 @@
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
+<?xml version='1.0'?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN"
+                      "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd" [
  <!ENTITY bookinfo SYSTEM "bookinfo.docbook">
  <!ENTITY introduction SYSTEM "introduction.docbook">
  <!ENTITY how-to-obtain SYSTEM "how-to-obtain.docbook">