Changeset b2a9f85

Timestamp:

09/21/2003 02:07:57 PM (20 years ago)

Author:

Larry Lawrence <larry@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/python-mods, qt5new, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

c4f1401

Parents:

36f9a23

Message:

acronym tagging

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1145 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:

• appendices/old/old.xml (modified) (1 diff)
• appendices/symlinks/symlinks.xml (modified) (1 diff)
• book/legalnotice.xml (modified) (1 diff)
• connect/dhcp/dhcpcd/dhcpcd-exp.xml (modified) (1 diff)
• general/graphlib/imlib2.xml (modified) (1 diff)
• introduction/important/bootscripts.xml (modified) (2 diffs)
• introduction/welcome/welcome.xml (modified) (1 diff)
• postlfs/config/config.xml (modified) (1 diff)
• postlfs/postlfs.xml (modified) (1 diff)
• pst/typesetting/sgml.xml (modified) (1 diff)
• pst/typesetting/xml.xml (modified) (1 diff)

appendices/old/old.xml

@@ -1 +1 @@
 <appendix role="dsssl" id="appendices-old">
 <?dbhtml filename="old.html" dir="appendices"?>
-<title>Packages which are no longer in the main BLFS Book</title>
+<title>Packages which are no longer in the main <acronym>BLFS</acronym> Book</title>
 
 <para>This appendix contains packages which have been deprecated from the
-main BLFS book for one reason or another.  The reason for their removal has
-been added to the top of the package instructions.  Note that in general
-these instructions are no longer maintained and will probably be removed in
-future releases.</para>
+main <acronym>BLFS</acronym> book for one reason or another.  The reason for 
+their removal has been added to the top of the package instructions.  Note that 
+in general these instructions are no longer maintained and will probably be 
+removed in future releases.</para>
 
 &gnome-common;

appendices/symlinks/symlinks.xml

@@ -1 +1 @@
 <appendix role="dsssl" id="appendices-symlinks">
 <?dbhtml filename="symlinks.html" dir="appendices"?>
-<title>List of rc?.d symlinks used in LFS/BLFS</title>
+<title>List of rc?.d symlinks used in <acronym>LFS</acronym>/<acronym>BLFS</acronym></title>
 
 <para>This section lists all of the symlinks used by the lfs-bootscripts
 package (correct as of version <userinput>1.9</userinput>) and all of
-the scripts in the BLFS book.  This is for two reasons:  first, so that
-you can see at a glance which number we have used for each package, and
-second so that <emphasis>we</emphasis> can see which number we have
-used for each package!  Without this, it would make our lives more
+the scripts in the <acronym>BLFS</acronym> book.  This is for two reasons:  
+first, so that you can see at a glance which number we have used for each 
+package, and second so that <emphasis>we</emphasis> can see which number we 
+have used for each package!  Without this, it would make our lives more
 difficult (as we'd probably end up with conflicts).</para>
 

book/legalnotice.xml

@@ -1 +1 @@
 <legalnotice>
 
-<para>Copyright (c) 2001-2003, BLFS Development Team</para>
+<para>Copyright (c) 2001-2003, <acronym>BLFS</acronym> Development Team</para>
 
 <para>All rights reserved.</para>

connect/dhcp/dhcpcd/dhcpcd-exp.xml

@@ -2 +2 @@
 <title>Command explanations</title>
 
-<para><userinput>patch -Np1 -i ../dhcpcd-&dhcpcd-version;.patch
-</userinput> : Dhcpcd unpatched puts all configuration and temporary
-files in <filename>/etc/dhcpc</filename>. This becomes very annoying
-when dhcpcd tells you it's running and it's not.  You look in
-<filename>/var/run</filename> for the pid file, but it's not there, the
-pid file that needs deleting is in <filename>/etc/dhcpc</filename>. This
-patch brings this program into FHS compliance, but more importantly,
-puts files where you expect them to be.</para>
+<para><command>patch -Np1 -i ../dhcpcd-&dhcpcd-version;.patch
+</command> : <application>Dhcpcd</application> unpatched puts all configuration 
+and temporary files in <filename>/etc/dhcpc</filename>. This becomes very 
+annoying when <application>dhcpcd</application> tells you it's running and it's 
+not.  You look in <filename>/var/run</filename> for the pid file, but it's not 
+there, the pid file that needs deleting is in <filename>/etc/dhcpc</filename>. 
+This patch brings this program into <acronym>FHS</acronym> compliance, but more 
+importantly, puts files where you expect them to be.</para>
 
-<para><userinput>--prefix=""</userinput> : There may be a good reason for
-abandoning the normal BLFS convention of using --prefix=/usr here.  If
-you are installing DHCP, it is likely that it is required during the
-boot process and <filename>/usr</filename> may be network mounted in which case, dhcpcd
-wouldn't be available due to being on the network!  Therefore, depending
-on your situation, you may want it to be installed in <filename>/sbin</filename> or <filename>/usr/sbin</filename>.  This command installs to <filename>/sbin</filename>.</para>
+<para><command>--prefix=""</command> : There may be a good reason for
+abandoning the normal <acronym>BLFS</acronym> convention of using --prefix=/usr 
+here.  If you are installing <acronym>DHCP</acronym>, it is likely that it is 
+required during the boot process and <filename>/usr</filename> may be network 
+mounted in which case, <command>dhcpcd</command> wouldn't be available due to 
+being on the network!  Therefore, depending on your situation, you may want it 
+to be installed in <filename>/sbin</filename> or <filename>/usr/sbin
+</filename>.  This command installs to <filename>/sbin</filename>.</para>
 
-<para><userinput>--sysconfdir=/var/lib</userinput> : This command install
+<para><command>--sysconfdir=/var/lib</command> : This command install
 configuration files in the <filename>/var/lib</filename>
 directory.</para>
 
-<para><userinput>--mandir=/usr/share/man</userinput> : This command
+<para><command>--mandir=/usr/share/man</command> : This command
 install the man pages to the <filename>/usr/share/man</filename>
 directory.</para>

general/graphlib/imlib2.xml

@@ -1 +1 @@
 <sect1 id="imlib2" xreflabel="Imlib2-&imlib2-version;">
-<?dbhtml filename="imlib2.html" dir="basicnet"?>
+<?dbhtml filename="imlib2.html" dir="general"?>
 <title>Imlib2-&imlib2-version;</title>
 

introduction/important/bootscripts.xml

@@ -1 +1 @@
 <sect1 id="intro-important-bootscripts">
 <?dbhtml filename="bootscripts.html" dir="introduction"?>
-<title>Using BLFS bootscripts</title>
+<title>Using <acronym>BLFS</acronym> bootscripts</title>
 
 <para>The scripts included for packages such as <xref linkend="gpm"/>
@@ -7 +7 @@
 the lfs-bootscripts package from version 3.2 and later of the <acronym>
 LFS</acronym> book. Note that this is lfs-bootscripts-1.6 and later (the old 
-numbering changed as of LFS-3.2).  The scripts won't work with versions
-of <acronym>LFS</acronym> before 3.2 because of a change in their organization 
-with the new scripts.  However, it should be trivial to adapt the scripts if 
-needed for older <acronym>LFS</acronym> versions.</para>
+numbering changed as of <acronym>LFS</acronym>-3.2).  The scripts won't work 
+with versions of <acronym>LFS</acronym> before 3.2 because of a change in their 
+organization with the new scripts.  However, it should be trivial to adapt the 
+scripts if needed for older <acronym>LFS</acronym> versions.</para>
 
 </sect1>

introduction/welcome/welcome.xml

@@ -1 +1 @@
 <chapter id="intro-welcome">
 <?dbhtml filename="welcome.html" dir="introduction"?>
-<title>Welcome to BLFS</title>
+<title>Welcome to <acronym>BLFS</acronym></title>
 <para>The Beyond Linux From Scratch book is designed to carry on from
 where the <acronym>LFS</acronym> book leaves off.  Unlike the <acronym>LFS

postlfs/config/config.xml

@@ -1 +1 @@
 <chapter id="postlfs-config">
 <?dbhtml filename="config.html" dir="postlfs"?>
-<title>After LFS Configuration Issues</title>
+<title>After <acronym>LFS</acronym> Configuration Issues</title>
 
-<para>The intention of LFS is to provide a basic system which you can
-build upon.  There are several things, about tidying up the system,
-which many people wonder about once they have done the base install.
+<para>The intention of <acronym>LFS</acronym> is to provide a basic system 
+which you can build upon.  There are several things, about tidying up the 
+system, which many people wonder about once they have done the base install.
 We hope to cover these issues in this chapter.</para>
 

postlfs/postlfs.xml

@@ -1 +1 @@
 <part id="postlfs" xreflabel="Post LFS Configuration and Extra Software">
 <?dbhtml filename="postlfs.html" dir="postlfs"?>
-<title>Post LFS Configuration and Extra Software</title>
+<title>Post <acronym>LFS</acronym> Configuration and Extra Software</title>
 
 &postlfs-config;

pst/typesetting/sgml.xml

@@ -1 +1 @@
 <chapter id="pst-sgml">
 <?dbhtml filename="sgml.html" dir="pst"?>
-<title>Standard Generalized Markup Language (SGML)</title>
+<title>Standard Generalized Markup Language (<acronym>SGML</acronym>)</title>
 
 &sgml-common;

pst/typesetting/xml.xml

@@ -1 +1 @@
 <chapter id="pst-xml">
 <?dbhtml filename="xml.html" dir="pst"?>
-<title>Extensible Markup Language (XML)</title>
+<title>Extensible Markup Language (<acronym>XML</acronym>)</title>
 
 &DocBook;