cvs commit: ALFS/docs/syntax_doc/preface acknowledgements.xml audience.xml contactinfo.xml conventions.xml

jwrober at linuxfromscratch.org jwrober at linuxfromscratch.org
Mon May 31 11:51:20 PDT 2004


jwrober     04/05/31 12:51:20

  Modified:    docs/syntax_doc/alfs_dtd alfs_dtd-intro.xml alfs_dtd.xml
                        elem_alfs.xml elem_content.xml elem_else.xml
                        elem_unpack.xml xml_dtd-syntax.xml
               docs/syntax_doc/book dedication.xml
               docs/syntax_doc/preface acknowledgements.xml audience.xml
                        contactinfo.xml conventions.xml
  Log:
  * Unused tag cleanup
  
  Revision  Changes    Path
  1.7       +4 -5      ALFS/docs/syntax_doc/alfs_dtd/alfs_dtd-intro.xml
  
  Index: alfs_dtd-intro.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/alfs_dtd-intro.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- alfs_dtd-intro.xml	29 May 2004 19:56:43 -0000	1.6
  +++ alfs_dtd-intro.xml	31 May 2004 18:51:20 -0000	1.7
  @@ -1,16 +1,15 @@
   <sect1 id="alfs_dtd-intro" xreflabel="&book-product; Introduction">
   <title>&book-product; Introduction</title>
   
  -<para><acronym>ALFS</acronym> profiles are written using an
  -<acronym>XML</acronym> syntax. This chapter describes the various
  -<acronym>XML</acronym> elements that can occur in a profile.</para>
  +<para>ALFS profiles are written using an XML syntax. This chapter describes
  +the various XML elements that can occur in a profile.</para>
   
   <para>For each element, the book describes:</para>
   
   <itemizedlist>
   
  -<listitem><para>the formal definition of the element, using the exact
  -<acronym>DTD</acronym> syntax</para></listitem>
  +<listitem><para>the formal definition of the element, using the exact DTD
  +syntax</para></listitem>
   
   <listitem><para>a description of the element</para></listitem>
   
  
  
  
  1.13      +1 -1      ALFS/docs/syntax_doc/alfs_dtd/alfs_dtd.xml
  
  Index: alfs_dtd.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/alfs_dtd.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- alfs_dtd.xml	29 May 2004 19:56:43 -0000	1.12
  +++ alfs_dtd.xml	31 May 2004 18:51:20 -0000	1.13
  @@ -1,6 +1,6 @@
   <chapter id="alfs_dtd" xreflabel="&book-product;">
   <?dbhtml filename="alfs_dtd/alfs_dtd.html"?>
  -<title>Description of the <acronym>ALFS</acronym> Profile Syntax</title>
  +<title>Description of the ALFS Profile Syntax</title>
   
   &alfs_dtd-intro;
   &xml_dtd-syntax;
  
  
  
  1.20      +4 -4      ALFS/docs/syntax_doc/alfs_dtd/elem_alfs.xml
  
  Index: elem_alfs.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/elem_alfs.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- elem_alfs.xml	29 May 2004 03:55:48 -0000	1.19
  +++ elem_alfs.xml	31 May 2004 18:51:20 -0000	1.20
  @@ -41,9 +41,9 @@
   <title>Description</title>
   
   <para>The element <filename>alfs</filename> is the root element of the
  -&book-product;. This means that an <acronym>ALFS</acronym> profile should
  -contain one and only one <filename>alfs</filename> element with all the other
  -elements being embedded within this element.</para>
  +&book-product;. This means that an ALFS profile should contain one and only
  +one <filename>alfs</filename> element with all the other elements being
  +embedded within this element.</para>
   
   <para>When processing an <filename>alfs</filename> element, one processes
   all its embedded children in their order of occurence.</para>
  @@ -53,7 +53,7 @@
   <filename>alfs</filename>. See <xref linkend="elem_base"/>.</para>
   
   <para>The attribute <filename>version</filename> identifies the version of
  -the <acronym>ALFS</acronym> profile syntax used; it should be
  +the ALFS profile syntax used; it should be
   <userinput>"3.1"</userinput>.</para>
   
   </sect2>
  
  
  
  1.10      +2 -3      ALFS/docs/syntax_doc/alfs_dtd/elem_content.xml
  
  Index: elem_content.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/elem_content.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- elem_content.xml	29 May 2004 03:55:48 -0000	1.9
  +++ elem_content.xml	31 May 2004 18:51:20 -0000	1.10
  @@ -22,9 +22,8 @@
   content of the file being created when processing a
   <filename>textdump</filename> operation.</para>
   
  -<note><para>Of course, it is possible to use <acronym>XML</acronym> entity
  -references in the <userinput>#PCDATA</userinput> or string of this
  -element.</para></note>
  +<note><para>Of course, it is possible to use XML entity references in the
  +<userinput>#PCDATA</userinput> or string of this element.</para></note>
   
   </sect2>
   
  
  
  
  1.7       +3 -3      ALFS/docs/syntax_doc/alfs_dtd/elem_else.xml
  
  Index: elem_else.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/elem_else.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- elem_else.xml	23 Feb 2004 03:09:50 -0000	1.6
  +++ elem_else.xml	31 May 2004 18:51:20 -0000	1.7
  @@ -43,9 +43,9 @@
   <sect2>
   <title>Description</title>
   
  -<para>This element groups the elements that should be executed if
  -the test performed when evaluating an <filename>if</filename> element isn't satisfied.
  -</para>
  +<para>This element groups the elements that should be executed if the test
  +performed when evaluating an <filename>if</filename> element isn't
  +satisfied.</para>
   
   </sect2>
   
  
  
  
  1.12      +2 -3      ALFS/docs/syntax_doc/alfs_dtd/elem_unpack.xml
  
  Index: elem_unpack.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/elem_unpack.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- elem_unpack.xml	29 May 2004 04:07:41 -0000	1.11
  +++ elem_unpack.xml	31 May 2004 18:51:20 -0000	1.12
  @@ -30,9 +30,8 @@
   operation elements.  It is used to unpack an archive into a destination
   directory</para>
   
  -<para>The sub-element <filename>reference</filename> gives the
  -<acronym>URL</acronym> of the archive, which is used if the archive file is
  -not available locally.</para>
  +<para>The sub-element <filename>reference</filename> gives the URL of the
  +archive, which is used if the archive file is not available locally.</para>
   
   <para>The sub-element <filename>digest</filename> gives the digest of the
   archive, as computed by openssl, using the digest type specified in the
  
  
  
  1.7       +62 -80    ALFS/docs/syntax_doc/alfs_dtd/xml_dtd-syntax.xml
  
  Index: xml_dtd-syntax.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/xml_dtd-syntax.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- xml_dtd-syntax.xml	3 Apr 2004 03:10:34 -0000	1.6
  +++ xml_dtd-syntax.xml	31 May 2004 18:51:20 -0000	1.7
  @@ -7,50 +7,39 @@
   
   <para>To ensure that all readers of the &book-product; Book get as much as
   possible from its contents, it is necessary to provide a quick introduction
  -to the concepts of <acronym>XML</acronym> and <acronym>DTD</acronym>
  -syntax.</para>
  +to the concepts of XML and DTD syntax.</para>
   
   <note><para>This introduction provides very few examples. This book is
  -written in an <acronym>XML</acronym> <acronym>DTD</acronym> called DocBook
  -<acronym>XML</acronym>. For an example of <acronym>XML</acronym> just look
  -at the book's source. Since this book is documenting an
  -<acronym>XML</acronym> <acronym>DTD</acronym>, look at the rest of the
  -book's contents for examples of <acronym>DTD</acronym>
  -syntax.</para></note>
  +written in an XML DTD called DocBook XML. For an example of XML just look
  +at the book's source. Since this book is documenting an XML DTD, look at
  +the rest of the book's contents for examples of DTD syntax.</para></note>
   
  -<para>To begin, here are some basic rules of
  -<acronym>XML</acronym> :</para>
  +<para>To begin, here are some basic rules of XML :</para>
   
   <itemizedlist>
   
  -<listitem><para><acronym>XML</acronym> documents use a self-describing and
  -simple to use syntax.</para></listitem>
  +<listitem><para>XML documents use a self-describing and simple to use
  +syntax.</para></listitem>
   
  -<listitem><para>All <acronym>XML</acronym> elements must have a closing
  -tag. With <acronym>XML</acronym>, it is illegal to omit the closing
  -tag.</para></listitem>
  -
  -<listitem><para><acronym>XML</acronym> tags are case
  -sensitive.</para></listitem>
  -
  -<listitem><para>All <acronym>XML</acronym> elements must be properly
  -nested. Improper nesting of tags makes no sense to
  -<acronym>XML</acronym>.</para></listitem>
  -
  -<listitem><para>All <acronym>XML</acronym> documents must have a root
  -element. In other words, all <acronym>XML</acronym> documents must contain
  -a single tag pair to define a root element.</para></listitem>
  -
  -<listitem><para>Attribute values must always be quoted. With
  -<acronym>XML</acronym>, it is illegal to omit quotation marks around
  -attribute values.</para></listitem>
  -
  -<listitem><para>With <acronym>XML</acronym>, white space is
  -preserved.</para></listitem>
  -
  -<listitem><para>With <acronym>XML</acronym>, <filename>CR</filename> /
  -<filename>LF</filename> is converted to
  -<filename>LF</filename></para></listitem>
  +<listitem><para>All XML elements must have a closing tag. With XML, it is
  +illegal to omit the closing tag.</para></listitem>
  +
  +<listitem><para>XML tags are case sensitive.</para></listitem>
  +
  +<listitem><para>All XML elements must be properly nested. Improper nesting
  +of tags makes no sense to XML.</para></listitem>
  +
  +<listitem><para>All XML documents must have a root element. In other words,
  +all XML documents must contain a single tag pair to define a root
  +element.</para></listitem>
  +
  +<listitem><para>Attribute values must always be quoted. With XML, it is
  +illegal to omit quotation marks around attribute values.</para></listitem>
  +
  +<listitem><para>With XML, white space is preserved.</para></listitem>
  +
  +<listitem><para>With XML, <filename>CR</filename> / <filename>LF</filename>
  +is converted to <filename>LF</filename></para></listitem>
   
   </itemizedlist>
   
  @@ -59,23 +48,21 @@
   <sect2>
   <title>XML Elements and Attributes</title>
   
  -<para><acronym>XML</acronym> is designed to hold any kind of information.
  -This information is stored in Elements. Elements are the basic building
  -blocks of <acronym>XML</acronym> and are represented in a
  -<acronym>XML</acronym> document as tag pairs. Attributes provide a
  -mechanism to further define or classify an element. Elements have
  -relationships with other elements in a document. Some are parents and some
  -are children. Using this semantic description, one can see that children
  -elements need parent elements defined and used first. As mentioned in the
  -last section, an <acronym>XML</acronym> document must have a root element.
  -Think of this as the ultimate parent element. The root element must be
  -defined and used before all other elements and all sub-elements (children).
  -All elements and sub-elements will reside inside of the root element. An
  -element can have parsed content, mixed content, simple content, empty
  -content or attributes in their definition.</para>
  +<para>XML is designed to hold any kind of information.  This information is
  +stored in Elements. Elements are the basic building blocks of XML and are
  +represented in a XML document as tag pairs. Attributes provide a mechanism
  +to further define or classify an element. Elements have relationships with
  +other elements in a document. Some are parents and some are children. Using
  +this semantic description, one can see that children elements need parent
  +elements defined and used first. As mentioned in the last section, an XML
  +document must have a root element.  Think of this as the ultimate parent
  +element. The root element must be defined and used before all other
  +elements and all sub-elements (children).  All elements and sub-elements
  +will reside inside of the root element. An element can have parsed content,
  +mixed content, simple content, empty content or attributes in their
  +definition.</para>
   
  -<para><acronym>XML</acronym> elements must follow these naming
  -rules :</para>
  +<para>XML elements must follow these naming rules :</para>
   
   <itemizedlist>
   
  @@ -95,31 +82,28 @@
   </sect2>
   
   <sect2>
  -<title>Quick Introduction to <acronym>DTD</acronym> Syntax</title>
  +<title>Quick Introduction to DTD Syntax</title>
   
  -<para>Once an <acronym>XML</acronym> document is written, it is generally a
  -good idea to validate the elements used in the document against a known
  -<acronym>DTD</acronym>. The Document Type Definition is the mechanism with
  -which one validates the content of a well-formed <acronym>XML</acronym>
  -document.</para>
  +<para>Once an XML document is written, it is generally a good idea to
  +validate the elements used in the document against a known DTD. The
  +Document Type Definition is the mechanism with which one validates the
  +content of a well-formed XML document.</para>
   
  -<para><acronym>XML</acronym> <acronym>DTD</acronym> files
  -contain :</para>
  +<para>XML DTD files contain :</para>
   
   <itemizedlist>
   
   <listitem><para><emphasis role="bold">Element declarations and
   definitions</emphasis> : Elements are declared and defined with
  -their relationships in the <acronym>DTD</acronym> file.</para></listitem>
  +their relationships in the DTD file.</para></listitem>
   
   <listitem><para><emphasis role="bold">Attribute declarations and
   definitions</emphasis> : Element classes or attributes are
  -declared and defined in the <acronym>DTD</acronym> file.</para></listitem>
  +declared and defined in the DTD file.</para></listitem>
   
   <listitem><para><emphasis role="bold">Entities</emphasis>
    :  Entities are the same thing as variables inside a
  -<acronym>DTD</acronym> file or <acronym>XML</acronym> document. They can
  -hold any kind of data.</para></listitem>
  +DTD file or XML document. They can hold any kind of data.</para></listitem>
   
   <listitem><para><emphasis role="bold"><filename>PCDATA</filename></emphasis>
    : <filename>PCDATA</filename> is Parsed Character DATA.
  @@ -138,11 +122,10 @@
   </sect2>
   
   <sect2>
  -<title><acronym>DTD</acronym> Element Declaration</title>
  +<title>DTD Element Declaration</title>
   
  -<para>Elements are declared in the <acronym>DTD</acronym> file using a
  -simple, but strict syntax.  There are four ways to define an
  -element :</para>
  +<para>Elements are declared in the DTD file using a simple, but strict
  +syntax.  There are four ways to define an element :</para>
   
   <itemizedlist>
   
  @@ -165,7 +148,7 @@
   <listitem><para><emphasis role="bold">With Children</emphasis>
    : When an element is declared with the names of other elements
   in it, this defines a parent-child relationship. Look in the
  -<acronym>DTD</acronym> for the child element names to be further defined
  +DTD for the child element names to be further defined
   with the other three ways.</para></listitem>
   
   <listitem><para><emphasis role="bold">Mixed</emphasis>
  @@ -175,9 +158,8 @@
   </itemizedlist>
   
   <para>When an element is declared with children, it will also define how
  -the children can be used inside an <acronym>XML</acronym> document.  There
  -are four ways that children elements can be defined in a
  -<acronym>DTD</acronym> file :</para>
  +the children can be used inside an XML document.  There are four ways that
  +children elements can be defined in a DTD file :</para>
   
   <itemizedlist>
   
  @@ -220,11 +202,11 @@
   </sect2>
   
   <sect2>
  -<title><acronym>DTD</acronym> Attribute Declaration</title>
  +<title>DTD Attribute Declaration</title>
   
  -<para>As mentioned above, attributes can help to define
  -"classes" of Elements. Attributes are defined with types and
  -values. There are 11 types :</para>
  +<para>As mentioned above, attributes can help to define "classes"
  +of Elements. Attributes are defined with types and values. There are 11
  +types :</para>
   
   <itemizedlist>
   
  @@ -244,11 +226,11 @@
    : The value is a list of other ids,</para></listitem>
   
   <listitem><para><emphasis role="bold"><filename>NMTOKEN</filename></emphasis>
  - : The value is a valid <acronym>XML</acronym>
  + : The value is a valid XML
   name.</para></listitem>
   
   <listitem><para><emphasis role="bold"><filename>NMTOKENS</filename></emphasis>
  - : The value is a list of valid <acronym>XML</acronym>
  + : The value is a list of valid XML
   names.</para></listitem>
   
   <listitem><para><emphasis role="bold"><filename>ENTITY</filename></emphasis>
  @@ -261,7 +243,7 @@
    : The value is a name of a notation.</para></listitem>
   
   <listitem><para><emphasis role="bold"><filename>xml</filename></emphasis>
  - : The value is a predefined <acronym>XML</acronym>
  + : The value is a predefined XML
   value.</para></listitem>
   
   </itemizedlist>
  
  
  
  1.3       +1 -2      ALFS/docs/syntax_doc/book/dedication.xml
  
  Index: dedication.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/book/dedication.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- dedication.xml	23 Feb 2004 03:04:22 -0000	1.2
  +++ dedication.xml	31 May 2004 18:51:20 -0000	1.3
  @@ -1,7 +1,6 @@
   <dedication role="xml">
   <title>Dedication</title>
   
  -<para>This book is dedicated to the <acronym>LFS</acronym> and 
  -<acronym>ALFS</acronym> communities.</para>
  +<para>This book is dedicated to the LFS and ALFS communities.</para>
   
   </dedication>
  
  
  
  1.7       +6 -6      ALFS/docs/syntax_doc/preface/acknowledgements.xml
  
  Index: acknowledgements.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/preface/acknowledgements.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- acknowledgements.xml	4 Nov 2003 02:48:54 -0000	1.6
  +++ acknowledgements.xml	31 May 2004 18:51:20 -0000	1.7
  @@ -8,23 +8,23 @@
   <itemizedlist>
   
   <listitem><para><ulink url="mailto:vassili at linuxfromscratch.org">Vassili
  -Dzuba</ulink>  <vassili at linuxfromscratch.org>  &emdash;
  -  for helping to create the <acronym>DTD</acronym> and writing
  +Dzuba</ulink>  <vassili at linuxfromscratch.org>  
  +&emdash;  for helping to create the DTD and writing
   the intial version of this book.</para></listitem>
   
   <listitem><para><ulink url="mailto:gerard at linuxfromscratch.org">Gerard
  -Beekmans</ulink>  <gerard at linuxfromscratch.org>  &emdash;
  -  for being more then a great help.</para></listitem>
  +Beekmans</ulink>  <gerard at linuxfromscratch.org>  
  +&emdash;  for being more then a great help.</para></listitem>
   
   <listitem><para><ulink url="mailto:jwrober at linuxfromscratch.org">James
   Robertson</ulink>  <jwrober at linuxfromscratch.org>  
   &emdash;  Current documentation editor.</para></listitem>
   
   <listitem><para>Jesse Tien-Ten-Que for helping to create the
  -<acronym>DTD</acronym> and writing the initial version of this
  +DTD and writing the initial version of this
   book.</para></listitem>
   
  -<listitem><para>Countless other people on the <acronym>ALFS</acronym> mailing
  +<listitem><para>Countless other people on the ALFS mailing
   list who are making this project happen by giving their suggestions, testing
   the tools and submitting bug reports.</para></listitem>
   
  
  
  
  1.7       +3 -4      ALFS/docs/syntax_doc/preface/audience.xml
  
  Index: audience.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/preface/audience.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- audience.xml	23 Feb 2004 03:04:43 -0000	1.6
  +++ audience.xml	31 May 2004 18:51:20 -0000	1.7
  @@ -3,10 +3,9 @@
   <title>Who Would Want To Read This Book</title>
   
   <para>This book is mainly aimed at those who want more information on the
  -&book-product;. The <acronym>DTD</acronym> is designed to be implementation
  -agnostic. This means that you may be reading this book as part of an
  -<acronym>ALFS</acronym> implementation source tarball or on the
  -<acronym>ALFS</acronym> website.</para>
  +&book-product;. The DTD is designed to be implementation agnostic. This
  +means that you may be reading this book as part of an ALFS implementation
  +source tarball or on the ALFS website.</para>
   
   </sect1>
   
  
  
  
  1.8       +26 -13    ALFS/docs/syntax_doc/preface/contactinfo.xml
  
  Index: contactinfo.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/preface/contactinfo.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- contactinfo.xml	23 Feb 2004 03:04:43 -0000	1.7
  +++ contactinfo.xml	31 May 2004 18:51:20 -0000	1.8
  @@ -8,17 +8,24 @@
   <para>The &book-product; uses two mailing list hosted from the Linux From
   Scratch servers.</para>
   
  -<para>Please direct the majority of your emails to the <acronym>ALFS</acronym> mailing list at
  +<para>Please direct the majority of your emails to the ALFS mailing list at
  +
   <ulink url="mailto:alfs-discuss at linuxfromscratch.org">alfs-discuss at linuxfromscratch.org</ulink>.
  -This is an excellent place to post questions and bug reports. For complete mailing list information, refer to
  -<ulink url="&http-root;/mailman/listinfo/alfs-discuss">&http-root;/mailman/listinfo/alfs-discuss</ulink>.
  -</para>
   
  -<para>The second list is really for the development team's use and is available at
  +This is an excellent place to post questions and bug reports. For complete
  +mailing list information, refer to
  +
  +<ulink url="&http-root;/mailman/listinfo/alfs-discuss">&http-root;/mailman/listinfo/alfs-discuss</ulink>.</para>
  +
  +<para>The second list is really for the development team's use and is
  +available at
  +
   <ulink url="mailto:alfs-log at linuxfromscratch.org">alfs-log at linuxfromscratch.org</ulink>.
  -This is an excellent place to see the daily activity of the project. For complete mailing list information, refer to
  -<ulink url="&http-root;/mailman/listinfo/alfs-log">&http-root;/mailman/listinfo/alfs-log</ulink>
  -</para>
  +
  +This is an excellent place to see the daily activity of the project. For
  +complete mailing list information, refer to
  +
  +<ulink url="&http-root;/mailman/listinfo/alfs-log">&http-root;/mailman/listinfo/alfs-log</ulink>.</para>
   
   </sect2>
   
  @@ -26,11 +33,13 @@
   <title>News Server</title>
   
   <para>All the mailing lists hosted at linuxfromscratch.org are also
  -accessible via the <acronym>NNTP</acronym> server. All messages posted to a
  -mailing list will be copied to its correspondent newsgroup, and vice versa.</para>
  +accessible via the NNTP server. All messages posted to a mailing list will
  +be copied to its correspondent newsgroup, and vice versa.</para>
   
   <para>The news server can be reached at
  +
   <ulink url="news:news.linuxfromscratch.org">news.linuxfromscratch.org</ulink>.
  +
   </para>
   
   </sect2>
  @@ -53,9 +62,13 @@
   <sect2>
   <title>Other</title>
   
  -<para>The current &book-product; documentation maintainer is &book-maintainer-fullname;.
  -If you need to reach &book-maintainer-firstname;, send an email to
  -<ulink url="mailto:&book-maintainer-address;">&book-maintainer-address;</ulink>.</para>
  +<para>The current &book-product; documentation maintainer is
  +&book-maintainer-fullname;. If you need to reach
  +&book-maintainer-firstname;, send an email to 
  +
  +<ulink url="mailto:&book-maintainer-address;">&book-maintainer-address;</ulink>.
  +
  +</para>
   
   </sect2>
   
  
  
  
  1.9       +1 -1      ALFS/docs/syntax_doc/preface/conventions.xml
  
  Index: conventions.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/preface/conventions.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- conventions.xml	29 May 2004 21:47:42 -0000	1.8
  +++ conventions.xml	31 May 2004 18:51:20 -0000	1.9
  @@ -39,7 +39,7 @@
   <blockquote><para>This type of section is used mainly when creating
   configuration files.  The first command (in bold) tells the system to create
   the file <filename>$LFS/etc/group</filename> from whatever is typed on the
  -following lines until the sequence <acronym>EOF</acronym> is encountered.
  +following lines until the sequence EOF is encountered.
   Therefore, this whole section is generally typed as seen.</para></blockquote>
   
   <note><para>Sample Note</para></note>
  
  
  



More information about the alfs-log mailing list