Bug#329988: Patch for Bug#329988: internal cross-references in the README.Debian

[Shyamal Prasad]

>>>>> "Marc" == Marc Haber <mh+debian-packages at zugschlus.de> writes:

    Marc> I have committed the patch to svn with the deviation that I
    Marc> didn't mention the macro name in the README text. I want
    Marc> people to read the documentation in the configuration file
    Marc> snippet.

In the interest of keeping that patch as small and clear as possible I
had not re-indented text where I normally would have. Sorry I did not
make this clear when I sent it.

There are a few dozen lines that need to be moved in 2 spaces to keep
with the structure of the document. If you wish to do this you can use
the patch below (it does not change any text, just adds white space a
refills a couple of lines).

Cheers!
Shyamal

Index: README.Debian.xml
===================================================================
--- README.Debian.xml	(revision 1321)
+++ README.Debian.xml	(working copy)
@@ -249,40 +249,41 @@
 	<command>update-exim4.conf.template</command>.
       </para>
       <section id='macros'>
-      <title>Using Exim Macros to control the configuration</title>
-      <para>
-	Our configuration can be controlled in a limited way by
-	setting macros. That way, you can switch on and off certain
-	parts of the default configuration without having to touch the
-	dpkg-conffiles. While touching dpkg-conffiles itself is
-	explitly allowed and wanted, it can be quite a nuisance to be
-	asked on package upgrade whether one wants to use the locally
-	changed file or the file changed by the package maintainer.
-      </para>
-      <para>
-	Whenever you see an <command>.ifdef</command> or
-	<command>.ifndef</command> clause in the configuration file,
-	you can control the appropriate clause by setting the macro in
-	a local configuration file. For split configuration, you can
-	drop the local configuration file anywhere in
-	<filename>/etc/exim4/conf.d/main</filename>. Just make sure it
-	gets read before the macro is first used. 
-	<filename>000_localmacros</filename> is a possible name,
-	guaranteeing first order. For a non-split configuration,
-	<filename>/etc/exim4/exim4.conf.localmacros</filename> gets
-	read before
-	<filename>/etc/exim4/exim4.conf.template</filename>. To
-	actually set the macro <varname>EXIM4_EXAMPLE</varname> to the
-	value "this is a sample", write the following line
-      </para>
-      <para>
-	EXIM4_EXAMPLE = this is a sample
-      </para>
-      <para>
-	into the appropriate file. For more detailed discussion of the
-	general macro mechanism, see the exim specification, chapter
-	6.4, for details how macro expansion works.
-      </para>
+	<title>Using Exim Macros to control the configuration</title>
+	<para>
+	  Our configuration can be controlled in a limited way by
+	  setting macros. That way, you can switch on and off certain
+	  parts of the default configuration without having to touch
+	  the dpkg-conffiles. While touching dpkg-conffiles itself is
+	  explitly allowed and wanted, it can be quite a nuisance to
+	  be asked on package upgrade whether one wants to use the
+	  locally changed file or the file changed by the package
+	  maintainer.
+        </para>
+	<para>
+	  Whenever you see an <command>.ifdef</command> or
+	  <command>.ifndef</command> clause in the configuration file,
+	  you can control the appropriate clause by setting the macro
+	  in a local configuration file. For split configuration, you
+	  can drop the local configuration file anywhere in
+	  <filename>/etc/exim4/conf.d/main</filename>. Just make sure
+	  it gets read before the macro is first used.
+	  <filename>000_localmacros</filename> is a possible name,
+	  guaranteeing first order. For a non-split configuration,
+	  <filename>/etc/exim4/exim4.conf.localmacros</filename> gets
+	  read before
+	  <filename>/etc/exim4/exim4.conf.template</filename>. To
+	  actually set the macro <varname>EXIM4_EXAMPLE</varname> to
+	  the value "this is a sample", write the following line
+        </para>
+	<para>
+	  EXIM4_EXAMPLE = this is a sample
+        </para>
+	<para>
+	  into the appropriate file. For more detailed discussion of
+	  the general macro mechanism, see the exim specification,
+	  chapter 6.4, for details how macro expansion works.
+        </para>
       </section>
       <section>
 	<title>What about debconf?</title>