Move punctuation/comma into quotes for <xref>s

We are using American rule for punctuation/comma vs. quotes.  We've
fixed most cases but not <xref>s.
This commit is contained in:
Xi Ruoyao 2024-06-22 11:43:31 +08:00
parent c04d98d038
commit 201aa93863
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
10 changed files with 18 additions and 15 deletions

View File

@ -13,7 +13,7 @@
<title>Udev configuration rules</title> <title>Udev configuration rules</title>
<para>The rules in this appendix are listed for convenience. Installation is <para>The rules in this appendix are listed for convenience. Installation is
normally done via instructions in <xref linkend='ch-system-udev'/>. </para> normally done via instructions in <xref linkend='ch-system-udev' role='.'/> </para>
<sect1 id="lfsrules" role="wrap"> <sect1 id="lfsrules" role="wrap">
<title>55-lfs.rules</title> <title>55-lfs.rules</title>

View File

@ -15,7 +15,7 @@
In case you've hit an issue building one package with the LFS In case you've hit an issue building one package with the LFS
instruction, we strongly discourage posting the issue directly onto instruction, we strongly discourage posting the issue directly onto
the upstream support channel before discussing via a LFS support the upstream support channel before discussing via a LFS support
channel listed in <xref linkend="ch-intro-resources"/>. channel listed in <xref linkend="ch-intro-resources" role='.'/>
Doing so is often quite inefficient because the upstream Doing so is often quite inefficient because the upstream
maintainers are rarely familiar with LFS building procedure. Even if maintainers are rarely familiar with LFS building procedure. Even if
you've really hit an upstream issue, the LFS community can still help you've really hit an upstream issue, the LFS community can still help

View File

@ -86,7 +86,7 @@
and, as <systemitem class="username">root</systemitem>, running the and, as <systemitem class="username">root</systemitem>, running the
commands in commands in
<xref linkend='ch-tools-bindmount'/> and <xref linkend='ch-tools-bindmount'/> and
<xref linkend='ch-tools-kernfsmount'/>.</para> <xref linkend='ch-tools-kernfsmount' role='.'/></para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</sect2> </sect2>

View File

@ -26,6 +26,6 @@
may render your computer unusable. may render your computer unusable.
This whole chapter must be done as user <systemitem This whole chapter must be done as user <systemitem
class="username">lfs</systemitem>, with the environment as described in class="username">lfs</systemitem>, with the environment as described in
<xref linkend="ch-preps-settingenviron"/>.</para> <xref linkend="ch-preps-settingenviron" role='.'/></para>
</sect1> </sect1>

View File

@ -88,7 +88,8 @@
make sure you have set <envar>LFS</envar>. make sure you have set <envar>LFS</envar>.
</para> </para>
<para> <para>
This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>. This has been discussed in
<xref linkend='ch-partitioning-aboutlfs' role='.'/>
</para> </para>
</important> </important>

View File

@ -111,7 +111,7 @@
mv -v /etc/bash_completion.d/grub /usr/share/bash-completion/completions</userinput></screen> mv -v /etc/bash_completion.d/grub /usr/share/bash-completion/completions</userinput></screen>
<para>Making your LFS system bootable with GRUB will be discussed in <para>Making your LFS system bootable with GRUB will be discussed in
<xref linkend="ch-bootable-grub"/>.</para> <xref linkend="ch-bootable-grub" role='.'/></para>
</sect2> </sect2>

View File

@ -242,7 +242,8 @@ useradd -D --gid 999</userinput></screen>
unknown GID 999</computeroutput>, unknown GID 999</computeroutput>,
even though the account has been created correctly. That is why we even though the account has been created correctly. That is why we
created the group <systemitem class="groupname">users</systemitem> created the group <systemitem class="groupname">users</systemitem>
with this group ID in <xref linkend='ch-tools-createfiles'/>.</para> with this group ID in
<xref linkend='ch-tools-createfiles' role='.'/></para>
</listitem> </listitem>
</varlistentry> </varlistentry>

View File

@ -39,7 +39,7 @@
often have two ethernet connections named eth0 and often have two ethernet connections named eth0 and
wlan0; such laptops can also use this method. The command line wlan0; such laptops can also use this method. The command line
is in the GRUB configuration file. is in the GRUB configuration file.
See <xref linkend="grub-cfg"/>.</para> See <xref linkend="grub-cfg" role='.'/></para>
</sect3> </sect3>
<sect3> <sect3>
@ -219,8 +219,8 @@
<title>Dealing with Duplicate Devices</title> <title>Dealing with Duplicate Devices</title>
<para>As explained in <xref linkend="ch-config-udev"/>, the order in <para>As explained in <xref linkend="ch-config-udev" role=','/> the
which devices with the same function appear in order in which devices with the same function appear in
<filename class="directory">/dev</filename> is essentially random. <filename class="directory">/dev</filename> is essentially random.
E.g., if you have a USB web camera and a TV tuner, sometimes E.g., if you have a USB web camera and a TV tuner, sometimes
<filename>/dev/video0</filename> refers to the camera and <filename>/dev/video0</filename> refers to the camera and
@ -229,8 +229,9 @@
For all classes of hardware except sound cards and network cards, this is For all classes of hardware except sound cards and network cards, this is
fixable by creating udev rules to create persistent symlinks. fixable by creating udev rules to create persistent symlinks.
The case of network cards is covered separately in The case of network cards is covered separately in
<xref linkend="ch-config-network"/>, and sound card configuration can <xref linkend="ch-config-network" role=','/> and sound card
be found in <ulink url="&blfs-book;postlfs/devices.html">BLFS</ulink>.</para> configuration can be found in
<ulink url="&blfs-book;postlfs/devices.html">BLFS</ulink>.</para>
<para>For each of your devices that is likely to have this problem <para>For each of your devices that is likely to have this problem
(even if the problem doesn't exist in your current Linux distribution), (even if the problem doesn't exist in your current Linux distribution),

View File

@ -254,7 +254,7 @@ EOF</userinput></screen>
/sys/class/rtc.</para> /sys/class/rtc.</para>
<para>For information on kernel module loading and udev, see <para>For information on kernel module loading and udev, see
<xref linkend="module-loading"/>.</para> <xref linkend="module-loading" role='.'/></para>
</sect2> </sect2>
<sect2 id="ch-config-clock"> <sect2 id="ch-config-clock">

View File

@ -55,8 +55,8 @@
LFS editors recommend that users not familiar with this process follow LFS editors recommend that users not familiar with this process follow
the procedures below fairly closely. The objective is to get an the procedures below fairly closely. The objective is to get an
initial system to a point where you can log in at the command line when initial system to a point where you can log in at the command line when
you reboot later in <xref linkend="ch-finish-reboot"/>. At this point you reboot later in <xref linkend="ch-finish-reboot" role='.'/>
optimization and customization is not a goal. At this point optimization and customization is not a goal.
</para> </para>