bpp-archindepdata: eliminate leading space, no change in content at all

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2178 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 063538a0d3e791d558e296e68b4ca1db4eb3c43c..fbf711d4c209ae9445b4bdfa37082b02d8eeef6e 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.182 $">
+  <!entity cvs-rev "$Revision: 1.183 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -3549,24 +3549,23 @@ Lisp packages should register themselves with
        sympa may be an example package
 -->    
 
-       <sect1 id="bpp-archindepdata">Architecture-independent data
-       <p>
-       It is not uncommon to have a large amount of architecture-independent
-       data packaged with a program. For example, collection of icons,
-       wallpapers or other graphic files, or audio files. If the size of
-       this data is negligible compared to the size of the remainder of the
-       package, you can keep it all in the same package.
-
-       <p>
-       However, if the size of the data is considerable, consider splitting
-       it out into a separate, architecture-independent package
-       ("_all.deb"). By doing this, you avoid needless duplication of the
-       same data into eleven or more .debs per each architecture. While
-       this adds some extra overhead into the Packages files, it can save a
-       lot of disk space on Debian mirrors, and it also reduces processing
-       time of Lintian or Linda when run over the entire Debian archive. 
-       </sect1>
-
+       <sect1 id="bpp-archindepdata">
+          <heading>Architecture-independent data</heading>
+          <p>
+It is not uncommon to have a large amount of architecture-independent
+data packaged with a program. For example, collection of icons,
+wallpapers or other graphic files, or audio files. If the size of
+this data is negligible compared to the size of the remainder of the
+package, you can keep it all in the same package.
+          <p>
+However, if the size of the data is considerable, consider splitting
+it out into a separate, architecture-independent package
+("_all.deb"). By doing this, you avoid needless duplication of the
+same data into eleven or more .debs per each architecture. While
+this adds some extra overhead into the Packages files, it can save a
+lot of disk space on Debian mirrors, and it also reduces processing
+time of Lintian or Linda when run over the entire Debian archive.
+        </sect1>
       </sect>
 
     </chapt>