Something I noticed recently, was that a small percentage of
linkend attributes in xref tags have the target within single
quotes, whereas the vast majority use double quotes, vis:
22992$ grep -r "linkend='" * | wc -l
68
22992$ grep -r "linkend=\"" * | wc -l
7855
Of the 68 occurences that the first grep finds, there
are only 38 files so afflicted, vis:
22992$ grep -lr "linkend='" * | wc -l
38
Those 38 files are shown here:
22992$ grep -lr "linkend='" *
archive/qt4.xml
archive/kde/core/config.xml
archive/kde/core/pre-install-config.xml
archive/udev.xml
archive/qt4.8.xml
archive/openssl.xml
archive/opal.xml
general/prog/ojdk-conf.xml
general/prog/lua52.xml
general.ent
introduction/important/la-files.xml
kde/plasma5/plasma-all.xml
multimedia/libdriv/mlt.xml
multimedia/libdriv/libsamplerate.xml
multimedia/libdriv/gst10-plugins-good.xml
multimedia/libdriv/frei0r.xml
multimedia/libdriv/libcanberra.xml
multimedia/libdriv/libao.xml
multimedia/libdriv/xine-lib.xml
multimedia/libdriv/gavl.xml
networking/netlibs/libtirpc.xml
networking/textweb/lynx.xml
postlfs/editors/mousepad.xml
postlfs/filesystems/aboutlvm.xml
postlfs/filesystems/lvm2.xml
postlfs/filesystems/aboutraid.xml
postlfs/config/devices.xml
postlfs/config/firmware.xml
postlfs/virtualization/qemu.xml
pst/typesetting/tex-path.xml
server/mail/sendmail.xml
x/installing/xorg7.xml
x/installing/xorg-config.xml
x/installing/mesa.xml
x/lib/qtwebengine.xml
x/lib/qt5.xml
xfce/apps/parole.xml
xsoft/other/balsa.xml
and an example of the mixing of quoting styles with a single souce
file can be seen in this stanza from the last of those files:
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="aspell"/>,
<xref linkend="enchant"/>,
<xref linkend="gmime"/>,
<xref linkend='gpgme'/>, and
<xref linkend="rarian"/>
</para>
where 'gpgme' is the "odd one out".
The reason I noticed this was that I had been trying to
perform a 'sed' on a set of files and found that my initial
attempt, which looked to operate on attributes with double
quotes, was falling a little way short of the desired result.
Whilst both quoting styles are valid, I thought that, in
the interests of consistency, I would present the attached
patch, which applies the double quote style across the Book,
in case more consistency was thought to to be desirable.
Kevin
Notes:
The patch does not alter files in the "archive" hierachy, though
maybe it should do, just in case any of those files are used as
"starters" for new content and/or returned to the Book in future.
The patch does not alter the "general.ent" file, where the single
quote style has been used within ENTITY definitions that, themselves,
are defined within double quotes.
The patch was created against a local tracking branch of the BLFS BOOK
trunk, hence the (revision 337) lines in the patch, although the
Book revision was 22992.
Index: general/prog/lua52.xml
===================================================================
--- general/prog/lua52.xml (revision 337)
+++ general/prog/lua52.xml (working copy)
@@ -42,7 +42,7 @@
<para>
This is an older verion of <application>Lua</application> needed only
- for compatibility with other programs such as <xref linkend='wireshark'/>.
+ for compatibility with other programs such as <xref linkend="wireshark"/>.
</para>
&lfs91_checked;
Index: general/prog/ojdk-conf.xml
===================================================================
--- general/prog/ojdk-conf.xml (revision 337)
+++ general/prog/ojdk-conf.xml (working copy)
@@ -21,7 +21,7 @@
<para>
After the package installation is complete, the next step is to make sure
that the system can properly find the files. If you set up your login
- scripts as recommended in <xref linkend='postlfs-config-profile'/>, update
+ scripts as recommended in <xref linkend="postlfs-config-profile"/>, update
the environment by creating the <filename>openjdk.sh</filename> script,
as the <systemitem class="username">root</systemitem> user:
</para>
Index: introduction/important/la-files.xml
===================================================================
--- introduction/important/la-files.xml (revision 337)
+++ introduction/important/la-files.xml (working copy)
@@ -60,7 +60,7 @@
<para>
The solution is to remove the .la files. However there is a catch.
- Some packages, such as <xref linkend='imagemagick'/>, use a libtool
+ Some packages, such as <xref linkend="imagemagick"/>, use a libtool
function, lt_dlopen, to load libraries as needed during execution and
resolve their dependencies at run time. In this case, the .la files
should remain.
Index: kde/plasma5/plasma-all.xml
===================================================================
--- kde/plasma5/plasma-all.xml (revision 337)
+++ kde/plasma5/plasma-all.xml (working copy)
@@ -109,7 +109,7 @@
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="glu"/>,
- <xref linkend='ibus'/>,
+ <xref linkend="ibus"/>,
<xref linkend="xorg-synaptics-driver"/>,
<ulink url="http://distributions.freedesktop.org/wiki/AppStream";>appstream-qt</ulink>,
<ulink url="https://www.kdevelop.org/";>KDevPlatform</ulink>,
Index: multimedia/libdriv/frei0r.xml
===================================================================
--- multimedia/libdriv/frei0r.xml (revision 337)
+++ multimedia/libdriv/frei0r.xml (working copy)
@@ -75,13 +75,13 @@
<bridgehead renderas="sect4">Recommended</bridgehead>
<para>
- <xref linkend='gavl'/>
+ <xref linkend="gavl"/>
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para>
- <xref linkend='doxygen'/> and
- <xref linkend='opencv'/> (currently broken)
+ <xref linkend="doxygen"/> and
+ <xref linkend="opencv"/> (currently broken)
</para>
Index: multimedia/libdriv/gavl.xml
===================================================================
--- multimedia/libdriv/gavl.xml (revision 337)
+++ multimedia/libdriv/gavl.xml (working copy)
@@ -78,12 +78,12 @@
<bridgehead renderas="sect4">Required</bridgehead>
<para>
- <xref linkend='libpng'/>
+ <xref linkend="libpng"/>
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para>
- <xref linkend='doxygen'/>
+ <xref linkend="doxygen"/>
</para>
<para condition="html" role="usernotes">User Notes:
Index: multimedia/libdriv/gst10-plugins-good.xml
===================================================================
--- multimedia/libdriv/gst10-plugins-good.xml (revision 337)
+++ multimedia/libdriv/gst10-plugins-good.xml (working copy)
@@ -115,7 +115,7 @@
<xref linkend="speex"/>,
<xref linkend="taglib"/>,
<xref linkend="valgrind"/>,
- <xref linkend='v4l-utils'/>,
+ <xref linkend="v4l-utils"/>,
<xref linkend="wayland"/>,
<ulink url="http://jackaudio.org/";>JACK</ulink>,
<ulink url="http://caca.zoy.org/wiki/libcaca";>libcaca</ulink>,
Index: multimedia/libdriv/libao.xml
===================================================================
--- multimedia/libdriv/libao.xml (revision 337)
+++ multimedia/libdriv/libao.xml (working copy)
@@ -81,7 +81,7 @@
<para role="optional">
<xref linkend="x-window-system"/>,
<xref linkend="alsa"/>, and
- <xref linkend='pulseaudio'/>
+ <xref linkend="pulseaudio"/>
</para>
<para condition="html" role="usernotes">User Notes:
Index: multimedia/libdriv/libcanberra.xml
===================================================================
--- multimedia/libdriv/libcanberra.xml (revision 337)
+++ multimedia/libdriv/libcanberra.xml (working copy)
@@ -90,7 +90,7 @@
<para role="optional">
<xref linkend="gtk2"/>,
<!--<xref linkend="gtk-doc"/>,-->
- <xref linkend='pulseaudio'/> and
+ <xref linkend="pulseaudio"/> and
<ulink url="http://tdb.samba.org/";>tdb</ulink>
</para>
Index: multimedia/libdriv/libsamplerate.xml
===================================================================
--- multimedia/libdriv/libsamplerate.xml (revision 337)
+++ multimedia/libdriv/libsamplerate.xml (working copy)
@@ -75,7 +75,7 @@
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
- <xref linkend='libsndfile'/> and
+ <xref linkend="libsndfile"/> and
<xref linkend="fftw"/> (for tests)
</para>
Index: multimedia/libdriv/mlt.xml
===================================================================
--- multimedia/libdriv/mlt.xml (revision 337)
+++ multimedia/libdriv/mlt.xml (working copy)
@@ -77,14 +77,14 @@
<bridgehead renderas="sect4">Required</bridgehead>
<para>
- <xref linkend='frei0r'/> and
- <xref linkend='qt5'/>
+ <xref linkend="frei0r"/> and
+ <xref linkend="qt5"/>
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para>
- <xref linkend='doxygen'/>,
- <xref linkend='fftw'/>,
+ <xref linkend="doxygen"/>,
+ <xref linkend="fftw"/>,
<xref linkend="libexif"/>,
<xref linkend="sdl"/>,
<ulink url="http://jackaudio.org";>JACK</ulink>,
Index: multimedia/libdriv/xine-lib.xml
===================================================================
--- multimedia/libdriv/xine-lib.xml (revision 337)
+++ multimedia/libdriv/xine-lib.xml (working copy)
@@ -80,7 +80,7 @@
<xref linkend="x-window-system"/>,
<xref linkend="ffmpeg"/>, and at least one of:
<xref linkend="alsa"/>,
- <xref linkend='pulseaudio'/>, or
+ <xref linkend="pulseaudio"/>, or
<ulink url="http://jackaudio.org/";>JACK</ulink>
</para>
Index: networking/netlibs/libtirpc.xml
===================================================================
--- networking/netlibs/libtirpc.xml (revision 337)
+++ networking/netlibs/libtirpc.xml (working copy)
@@ -90,7 +90,7 @@
<note>
<para>
If updating this package, you will also need to update
- any existing version of <xref linkend='rpcbind'/>
+ any existing version of <xref linkend="rpcbind"/>
</para>
</note>
<!-- Looks like this is incorporated in version 1.0.3
Index: networking/textweb/lynx.xml
===================================================================
--- networking/textweb/lynx.xml (revision 337)
+++ networking/textweb/lynx.xml (working copy)
@@ -99,7 +99,7 @@
<xref linkend="unzip"/>,
an <xref linkend="server-mail"/> (that provides a
<command>sendmail</command> command), and
- <xref linkend='sharutils'/> (for a <command>uudecode</command> program)
+ <xref linkend="sharutils"/> (for a <command>uudecode</command> program)
</para>
<!-- Attempt to utilize S-Lang (- -with-screen=slang) leads to a build failure -->
Index: postlfs/config/devices.xml
===================================================================
--- postlfs/config/devices.xml (revision 337)
+++ postlfs/config/devices.xml (working copy)
@@ -151,7 +151,7 @@
<para>
The above line is used for descriptive purposes only. The
scanner <application>udev</application> rules are put into place when
- installing <xref linkend='sane'/>.
+ installing <xref linkend="sane"/>.
</para>
</note>
Index: postlfs/config/firmware.xml
===================================================================
--- postlfs/config/firmware.xml (revision 337)
+++ postlfs/config/firmware.xml (working copy)
@@ -268,7 +268,7 @@
<para>
If the microcode was not updated, there is no new microcode for this
system's processor. If it did get updated, you can now proceed to
- <xref linkend='early-microcode'/>.
+ <xref linkend="early-microcode"/>.
</para>
</sect3>
@@ -332,7 +332,7 @@
<para>
If the microcode was not updated, there is no new microcode for
this system's processor. If it did get updated, you can now proceed to
- <xref linkend='early-microcode'/>.
+ <xref linkend="early-microcode"/>.
</para>
</sect3>
@@ -343,7 +343,7 @@
<para>
If you have established that updated microcode is available for
your system, it is time to prepare it for early loading. This requires
- an additional package, <xref linkend='cpio'/> and the creation of an
+ an additional package, <xref linkend="cpio"/> and the creation of an
initrd which will need to be added to grub.cfg.
</para>
@@ -466,7 +466,7 @@
</para>
<para>
- A better approach is to install <xref linkend='pciutils'/> and then
+ A better approach is to install <xref linkend="pciutils"/> and then
use <userinput>lspci</userinput> to identify which VGA controller is
installed.
</para>
@@ -585,7 +585,7 @@
<para>
Identifying the correct firmware will typically require you to install
- <xref linkend='pciutils'/>, and then use <userinput>lspci</userinput>
+ <xref linkend="pciutils"/>, and then use <userinput>lspci</userinput>
to identify the device. You should then search online to check which
module it uses, which firmware, and where to obtain the firmware —
not all of it is in linux-firmware.
@@ -594,8 +594,8 @@
<para>
If possible, you should begin by using a wired connection when you first
boot your LFS system. To use a wireless connection you will need to
- use a network tools such as <xref linkend='wireless_tools'/> and <xref
- linkend='wpa_supplicant'/>.
+ use a network tools such as <xref linkend="wireless_tools"/> and <xref
+ linkend="wpa_supplicant"/>.
</para>
<para>
Index: postlfs/editors/mousepad.xml
===================================================================
--- postlfs/editors/mousepad.xml (revision 337)
+++ postlfs/editors/mousepad.xml (working copy)
@@ -83,7 +83,7 @@
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
- <xref role="runtime" linkend='dconf'/> (runtime) and
+ <xref role="runtime" linkend="dconf"/> (runtime) and
<xref linkend="dbus-glib"/>
</para>
@@ -120,7 +120,7 @@
<para>
<parameter>--enable-keyfile-settings</parameter>: Use the GSettings
- keyfile backend rather than the default <xref linkend='dconf'/>.
+ keyfile backend rather than the default <xref linkend="dconf"/>.
</para>
</sect2>
Index: postlfs/filesystems/aboutlvm.xml
===================================================================
--- postlfs/filesystems/aboutlvm.xml (revision 337)
+++ postlfs/filesystems/aboutlvm.xml (working copy)
@@ -29,7 +29,7 @@
</para>
<para>
- To run any of the commands presented here, the <xref linkend='lvm2'/>
+ To run any of the commands presented here, the <xref linkend="lvm2"/>
package must be installed. All commands must be run as the <systemitem
class="username">root</systemitem> user.
</para>
@@ -123,7 +123,7 @@
<para>
Finally the logical volumes can be formatted and mounted. In this
- example, the jfs file system (<xref linkend='jfsutils'/>) is used for
+ example, the jfs file system (<xref linkend="jfsutils"/>) is used for
demonstration purposes.
</para>
Index: postlfs/filesystems/aboutraid.xml
===================================================================
--- postlfs/filesystems/aboutraid.xml (revision 337)
+++ postlfs/filesystems/aboutraid.xml (working copy)
@@ -35,7 +35,7 @@
Note that while RAID provides protection against disk
failures, it is not a substitute for backups. A file deleted
is still deleted on all the disks of a RAID array. Modern backups
- are generally done via <xref linkend='rsync'/>.
+ are generally done via <xref linkend="rsync"/>.
</para>
<para>
@@ -99,7 +99,7 @@
Software based RAID is the most flexible form of RAID. It is
easy to install and update and provides full capability on all or
part of any drives available to the system. In BLFS, the RAID software
- is found in <xref linkend='mdadm'/>.
+ is found in <xref linkend="mdadm"/>.
</para>
<para>
@@ -111,7 +111,7 @@
<para>
The first step in creating a RAID array is to use partitioning software
- such as <userinput>fdisk</userinput> or <xref linkend='parted'/> to
+ such as <userinput>fdisk</userinput> or <xref linkend="parted"/> to
define the partitions needed for the array. Usually, there will be
one partition on each drive participating in the RAID array, but that
is not strictly necessary. For this example, there will be four disk
@@ -198,8 +198,8 @@
<para>
From this point, the partitions can be formated with the filesystem of
- choice (e.g. ext3, ext4, <xref linkend='xfsprogs'/>, <xref
- linkend='reiserfs'/>, etc). The formatted partitions can then be
+ choice (e.g. ext3, ext4, <xref linkend="xfsprogs"/>, <xref
+ linkend="reiserfs"/>, etc). The formatted partitions can then be
mounted. The <filename>/etc/fstab</filename> file can use the devices
created for mounting at boot time and the linux command line in
<filename>/boot/grub/grub.cfg</filename> can specify
Index: postlfs/filesystems/lvm2.xml
===================================================================
--- postlfs/filesystems/lvm2.xml (revision 337)
+++ postlfs/filesystems/lvm2.xml (working copy)
@@ -78,16 +78,16 @@
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
- <xref linkend='libaio'/>
+ <xref linkend="libaio"/>
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
- <xref linkend='mdadm'/>,
- <xref linkend='reiserfs'/>,
- <xref linkend='valgrind'/>,
- <xref linkend='which'/>,
- <xref linkend='xfsprogs'/> (all five may be used, but are not required,
+ <xref linkend="mdadm"/>,
+ <xref linkend="reiserfs"/>,
+ <xref linkend="valgrind"/>,
+ <xref linkend="which"/>,
+ <xref linkend="xfsprogs"/> (all five may be used, but are not required,
for tests), and
<ulink url='https://github.com/jthornber/thin-provisioning-tools'>
thin-provisioning-tools</ulink>
Index: postlfs/virtualization/qemu.xml
===================================================================
--- postlfs/virtualization/qemu.xml (revision 337)
+++ postlfs/virtualization/qemu.xml (working copy)
@@ -163,7 +163,7 @@
<para>
To use the <quote>bridge</quote> network device, as explained below,
- check that <xref linkend='bridgeutils'/> is installed
+ check that <xref linkend="bridgeutils"/> is installed
and the following options in the kernel configuration are enabled:
</para>
Index: pst/typesetting/tex-path.xml
===================================================================
--- pst/typesetting/tex-path.xml (revision 337)
+++ pst/typesetting/tex-path.xml (working copy)
@@ -18,7 +18,7 @@
<para>
Before starting to build TeX Live, set up your PATH so
that the system can properly find the files. If you set up your login
- scripts as recommended in <xref linkend='postlfs-config-profile'/>, update
+ scripts as recommended in <xref linkend="postlfs-config-profile"/>, update
the needed paths by appending to the
<filename>extrapaths.sh</filename> script. The programs are always
installed in an <ARCH>-linux subdirectory and on 32-bit x86 this is
Index: server/mail/sendmail.xml
===================================================================
--- server/mail/sendmail.xml (revision 337)
+++ server/mail/sendmail.xml (working copy)
@@ -244,7 +244,7 @@
<para>
<command>sed ... include/sm/bdb.h</command>: This allows sendmail to
- build properly with <xref linkend='db'/> versions 5 and above.
+ build properly with <xref linkend="db"/> versions 5 and above.
</para>
<para>
Index: x/installing/mesa.xml
===================================================================
--- x/installing/mesa.xml (revision 337)
+++ x/installing/mesa.xml (working copy)
@@ -113,9 +113,9 @@
to as llvmpipe. See <ulink role="nodep"
url="http://www.mesa3d.org/systems.html"/> for more information), and
<xref linkend="wayland-protocols"/> (required for
- <xref role="nodep" linkend='plasma5-build'/>,
- <!-- <xref role="nodep" linkend='lxqt'/>, -->
- GNOME, and recommended for <xref role="nodep" linkend='gtk3'/>)
+ <xref role="nodep" linkend="plasma5-build"/>,
+ <!-- <xref role="nodep" linkend="lxqt"/>, -->
+ GNOME, and recommended for <xref role="nodep" linkend="gtk3"/>)
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
Index: x/installing/xorg-config.xml
===================================================================
--- x/installing/xorg-config.xml (revision 337)
+++ x/installing/xorg-config.xml (working copy)
@@ -66,7 +66,7 @@
<para>
Generally, there is no specific configuration required for
<application>Xorg</application>, but customization is possible. For
- details, see <xref linkend='xconfig'/> below.
+ details, see <xref linkend="xconfig"/> below.
</para>
</sect2>
Index: x/installing/xorg7.xml
===================================================================
--- x/installing/xorg7.xml (revision 337)
+++ x/installing/xorg7.xml (working copy)
@@ -173,7 +173,7 @@
<para>
If you've decided to use the standard <filename
class="directory">/usr</filename> prefix, you can omit the remainder of
- this page and continue at <xref linkend='util-macros'/>.
+ this page and continue at <xref linkend="util-macros"/>.
</para>
</note>
Index: x/lib/qt5.xml
===================================================================
--- x/lib/qt5.xml (revision 337)
+++ x/lib/qt5.xml (working copy)
@@ -376,7 +376,7 @@
EOF</userinput></screen>
<para>
- Some packages such as <xref linkend='vlc'/> look for certain
+ Some packages such as <xref linkend="vlc"/> look for certain
executables with a -qt5 suffix. Run the following command as the
<systemitem class="username">root</systemitem> user
to create the necessary symlinks:
Index: x/lib/qtwebengine.xml
===================================================================
--- x/lib/qtwebengine.xml (revision 337)
+++ x/lib/qtwebengine.xml (working copy)
@@ -112,7 +112,7 @@
<para role="required">
<xref linkend="nss"/>,
<xref linkend="python2"/>, and
- <xref linkend='qt5'/>
+ <xref linkend="qt5"/>
</para>
<bridgehead renderas="sect4">Recommended</bridgehead>
Index: xfce/apps/parole.xml
===================================================================
--- xfce/apps/parole.xml (revision 337)
+++ xfce/apps/parole.xml (working copy)
@@ -128,7 +128,7 @@
<para>
<option>--with-gstreamer=1.0</option>: Use this switch if both
- the <xref linkend='gstreamer10'/> and the deprecated gstreamer-0.x
+ the <xref linkend="gstreamer10"/> and the deprecated gstreamer-0.x
packages are installed.
</para>
Index: xsoft/other/balsa.xml
===================================================================
--- xsoft/other/balsa.xml (revision 337)
+++ xsoft/other/balsa.xml (working copy)
@@ -77,7 +77,7 @@
<xref linkend="aspell"/>,
<xref linkend="enchant"/>,
<xref linkend="gmime"/>,
- <xref linkend='gpgme'/>, and
+ <xref linkend="gpgme"/>, and
<xref linkend="rarian"/>
</para>
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
