Changeset 360fdfca


Ignore:
Timestamp:
01/26/2024 05:28:53 PM (3 months ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
12.1, 12.1-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc
Children:
0d80918a, f6a43f6
Parents:
44850bb
Message:

Fix punctuation in quotes, and quote signs

  • period and comma inside quotes
  • " to <quote>
  • some " to <literal> when it is a var value
Files:
21 edited

Legend:

Unmodified
Added
Removed

  • chapter02/hostreqs.xml

    r44850bb r360fdfca  
    3131    place software headers into separate packages, often in the form of
    3232    <quote>&lt;package-name&gt;-devel</quote> or
    33     <quote>&lt;package-name&gt;-dev</quote>. Be sure to install those if
     33    <quote>&lt;package-name&gt;-dev.</quote> Be sure to install those if
    3434    your distribution provides them.</para>
    3535

  • chapter02/mounting.xml

    r44850bb r360fdfca  
    1717  </para>
    1818 
    19   <para>Strictly speaking, one cannot "mount a partition". One mounts the <emphasis>file
     19  <para>Strictly speaking, one cannot "mount a partition." One mounts the <emphasis>file
    2020  system</emphasis> embedded in that partition. But since a single partition can't contain
    2121  more than one file system, people often speak of the partition and the

  • chapter02/stages.xml

    r44850bb r360fdfca  
    7070      <listitem>
    7171        <para>A few operations, from <quote>Changing Ownership</quote> to
    72         <quote>Entering the Chroot Environment</quote>, must be done as the
     72        <quote>Entering the Chroot Environment,</quote> must be done as the
    7373        <systemitem class="username">root</systemitem> user, with the LFS
    7474        environment variable set for the &root; user.</para>

  • chapter05/glibc.xml

    r44850bb r360fdfca  
    160160
    161161    <note><para>There have been reports that this package may fail when
    162     building as a "parallel make".  If that occurs, rerun the make command
    163     with the "-j1" option.</para></note>
     162    building as a <quote>parallel make.</quote>  If that occurs, rerun the make command
     163    with the <option>-j1</option> option.</para></note>
    164164
    165165    <para>Compile the package:</para>

  • chapter06/file.xml

    r44850bb r360fdfca  
    7979<screen><userinput remap="configure">./configure --prefix=/usr --host=$LFS_TGT --build=$(./config.guess)</userinput></screen>
    8080
    81 <!-- devs: if using - -build here, the build system wants to compile
    82      the signature file with "file" on the build system, but stops if it is not
    83      the same version. One possibility would be to build "file" on the build
    84      system first, but it is simpler to have the system think it is not
    85      cross-compiling, and use the just built "file". -->
    8681    <para>Compile the package:</para>
    8782

  • chapter07/python.xml

    r44850bb r360fdfca  
    4646    <note>
    4747      <para>There are two package files whose name starts with
    48       <quote>python</quote>. The one to extract from is
     48      <quote>python.</quote> The one to extract from is
    4949      <filename>Python-&python-version;.tar.xz</filename> (notice the
    5050      uppercase first letter).</para>

  • chapter08/coreutils.xml

    r44850bb r360fdfca  
    12621262        <term><command>yes</command></term>
    12631263        <listitem>
    1264           <para>Repeatedly outputs <quote>y</quote>, or a given string, until
     1264          <para>Repeatedly outputs <quote>y,</quote> or a given string, until
    12651265          killed</para>
    12661266          <indexterm zone="ch-system-coreutils yes">

  • chapter08/expect.xml

    r44850bb r360fdfca  
    9393
    9494    <para>If any test fails with the message
    95     <quote><computeroutput>The system has no more ptys.  Ask your system
    96     administrator to create more</computeroutput></quote>, it indicates
     95    <quote><computeroutput>The system has no more ptys. Ask your system
     96    administrator to create more</computeroutput>,</quote> it indicates
    9797    you've not mounted the
    9898    <systemitem class="filesystem">devpts</systemitem> file system

  • chapter08/gmp.xml

    r44850bb r360fdfca  
    5959
    6060      <!-- To editors: the configure script says "the none host is obsolete,
    61            use - -disable-assembly", but don't believe it: with the latter
     61           use - -disable-assembly," but don't believe it: with the latter
    6262           CFLAGS is still automatically set to -march=something.  -->
    6363    </note>
    … …  
    107107    it is built. Occasionally, the code that detects the processor misidentifies
    108108    the system capabilities and there will be errors in the tests or other
    109     applications using the gmp libraries with the message "Illegal
    110     instruction".  In this case, gmp should be reconfigured with the option
     109    applications using the gmp libraries with the message
     110    <computeroutput>Illegal instruction</computeroutput>.
     111    In this case, gmp should be reconfigured with the option
    111112    <option>--host=none-linux-gnu</option> and rebuilt.</para></caution>
    112113

  • chapter08/stripping.xml

    r44850bb r360fdfca  
    5353  and ld-linux.so.2 on 32-bit systems.  The construct below selects the
    5454  correct name for the current architecture, excluding anything ending
    55   with <quote>g</quote>, in case the commands below have already been
     55  with <quote>g,</quote> in case the commands below have already been
    5656  run.</para></note>
    5757

  • chapter09/consoled.xml

    r44850bb r360fdfca  
    3131
    3232  <para>The <filename>/etc/vconsole.conf</filename> file should contain lines
    33   of the form: VARIABLE="value". The following variables are recognized:</para>
     33  of the form: <envar>VARIABLE=value</envar>. The following variables are recognized:</para>
    3434
    3535  <variablelist>

  • chapter09/locale.xml

    r44850bb r360fdfca  
    4040
    4141  <para>Replace <replaceable>&lt;ll&gt;</replaceable> below with the two-letter code
    42   for your desired language (e.g., <quote>en</quote>) and
     42  for your desired language (e.g., <literal>en</literal>) and
    4343  <replaceable>&lt;CC&gt;</replaceable> with the two-letter code for the appropriate
    44   country (e.g., <quote>GB</quote>). <replaceable>&lt;charmap&gt;</replaceable> should
     44  country (e.g., <literal>GB</literal>). <replaceable>&lt;charmap&gt;</replaceable> should
    4545  be replaced with the canonical charmap for your chosen locale. Optional
    46   modifiers such as <quote>@euro</quote> may also be present.</para>
     46  modifiers such as <literal>@euro</literal> may also be present.</para>
    4747
    4848  <para>The list of all locales supported by Glibc can be obtained by running
    … …  
    5252
    5353  <para>Charmaps can have a number of aliases, e.g., <quote>ISO-8859-1</quote>
    54   is also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
     54  is also referred to as <quote>iso8859-1</quote> and <quote>iso88591.</quote>
    5555  Some applications cannot handle the various synonyms correctly (e.g., require
    56   that <quote>UTF-8</quote> is written as <quote>UTF-8</quote>, not
    57   <quote>utf8</quote>), so it is the safest in most
     56  that <quote>UTF-8</quote> is written as <literal>UTF-8,</literal> not
     57  <literal>utf8</literal>), so it is the safest in most
    5858  cases to choose the canonical name for a particular locale. To determine
    5959  the canonical name, run the following command, where <replaceable>&lt;locale
    … …  
    6868<screen><computeroutput>ISO-8859-1</computeroutput></screen>
    6969
    70   <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
     70  <para>This results in a final locale setting of <literal>en_GB.ISO-8859-1</literal>.
    7171  It is important that the locale found using the heuristic above is tested prior
    7272  to it being added to the Bash startup files:</para>
    … …  
    9090  Further instructions assume that there are no such error messages from
    9191  Glibc.</para>
    92 
    93   <!-- FIXME: the xlib example will become obsolete in the future.-->
    94   <para>Some packages beyond LFS may also lack support for your chosen locale. One
    95   example is the X library (part of the X Window System), which outputs the
    96   following error message if the locale does not exactly match one of the character
    97   map names in its internal files:</para>
    98 
    99 <screen><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></screen>
    100 
    101   <para>In several cases Xlib expects that the character map will be listed in
    102   uppercase notation with canonical dashes. For instance, "ISO-8859-1" rather
    103   than "iso88591". It is also  possible to find an appropriate specification by
    104   removing the charmap part of the locale specification.  This can be checked
    105   by running the <command>locale charmap</command> command in both locales.
    106   For example, one would have to change "de_DE.ISO-8859-15@euro" to
    107   "de_DE@euro" in order to get this locale recognized by Xlib.</para>
    10892
    10993  <para>Other packages can also function incorrectly (but may not necessarily

  • chapter09/network.xml

    r44850bb r360fdfca  
    6363    the interfaces up correctly.</para>
    6464
    65     <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the
     65    <para>If the <envar>ONBOOT</envar> variable is set to <literal>yes</literal> the
    6666    System V network script will bring up the Network Interface Card (NIC) during
    67     the system boot process. If set to anything besides <quote>yes</quote>, the NIC
     67    the system boot process. If set to anything besides <literal>yes</literal>, the NIC
    6868    will be ignored by the network script and will not be started automatically.
    6969    Interfaces can be manually started or stopped with the

  • chapter09/networkd.xml

    r44850bb r360fdfca  
    9999        <listitem>
    100100          <para>
    101              Create a manual naming scheme, for example by naming the
    102              interfaces something like "internet0", "dmz0", or "lan0".
    103              To do that, create .link files in /etc/systemd/network/ that
    104              select an explicit name or a better naming scheme for your
    105              network interfaces. For example:
     101            Create a manual naming scheme, for example by naming the
     102            interfaces something like <literal>internet0</literal>,
     103            <literal>dmz0</literal>, or <literal>lan0</literal>.
     104            To do that, create .link files in /etc/systemd/network/ that
     105            select an explicit name or a better naming scheme for your
     106            network interfaces. For example:
    106107          </para>
    107108

  • chapter09/profile.xml

    r44850bb r360fdfca  
    7676
    7777  <para>Charmaps can have a number of aliases, e.g., <quote>ISO-8859-1</quote>
    78   is also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
     78  is also referred to as <quote>iso8859-1</quote> and <quote>iso88591.</quote>
    7979  Some applications cannot handle the various synonyms correctly (e.g., require
    80   that <quote>UTF-8</quote> is written as <quote>UTF-8</quote>, not
    81   <quote>utf8</quote>), so it is safest in most
     80  that <quote>UTF-8</quote> is written as <literal>UTF-8</literal>, not
     81  <literal>utf8</literal>), so it is safest in most
    8282  cases to choose the canonical name for a particular locale. To determine
    8383  the canonical name, run the following command, where <replaceable>&lt;locale
    … …  
    9292<screen><computeroutput>ISO-8859-1</computeroutput></screen>
    9393
    94   <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
     94  <para>This results in a final locale setting of <literal>en_GB.ISO-8859-1</literal>.
    9595  It is important that the locale found using the heuristic above is tested before
    9696  it is added to the Bash startup files:</para>
    … …  
    115115  Glibc.</para>
    116116
    117   <!-- FIXME: the xlib example will became obsolete real soon -->
    118   <!--<para>Some packages beyond LFS may also lack support for your chosen locale. One
    119   example is the X library (part of the X Window System), which outputs the
    120   following error message if the locale does not exactly match one of the character
    121   map names in its internal files:</para>
    122 
    123 <screen><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></screen>
    124 
    125   <para>In several cases Xlib expects that the character map will be listed in
    126   uppercase notation with canonical dashes. For instance, "ISO-8859-1" rather
    127   than "iso88591". It is also  possible to find an appropriate specification by
    128   removing the charmap part of the locale specification.  This can be checked
    129   by running the <command>locale charmap</command> command in both locales.
    130   For example, one would have to change "de_DE.ISO-8859-15@euro" to
    131   "de_DE@euro" in order to get this locale recognized by Xlib.</para>
    132 -->
    133117  <para>Other packages may also function incorrectly (but will not necessarily
    134118  display any error messages) if the locale name does not meet their expectations.

  • chapter09/udev.xml

    r44850bb r360fdfca  
    130130      supported by a module. For example, the <emphasis>snd-fm801</emphasis>
    131131      driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801,
    132       and has an alias of <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.
     132      and has an alias of <literal>pci:v00001319d00000801sv*sd*bc04sc01i*</literal>.
    133133      For most devices, the bus driver exports the alias of the driver that
    134134      would handle the device via <systemitem
    … …  
    136136      <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file
    137137      might contain the string
    138       <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
     138      <literal>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</literal>.
    139139      The default rules provided with udev will cause <command>udevd</command>
    140140      to call out to <command>/sbin/modprobe</command> with the contents of the
    … …  
    302302      <para>This is due to the fact that udev, by design, handles uevents and
    303303      loads modules in parallel, and thus in an unpredictable order. This will
    304       never be <quote>fixed</quote>. You should not rely upon the kernel device
     304      never be <quote>fixed.</quote> You should not rely upon the kernel device
    305305      names being stable. Instead, create your own rules that make symlinks with
    306306      stable names based on some stable attributes of the device, such as a

  • chapter09/usage.xml

    r44850bb r360fdfca  
    4949    <note>
    5050       <para>
    51           Classically, run level 2 above was defined as
    52           "multi-user mode without networking", but this was only the case
    53           many years ago when multiple users could connect to a system via
    54           serial ports.  In today's environment it makes no sense, and
    55           we now say it is "reserved".
     51         Classically, run level 2 above was defined as <quote>multi-user
     52         mode without networking,</quote> but this was only the case
     53         many years ago when multiple users could connect to a system via
     54         serial ports.  In today's environment it makes no sense, and
     55         we now say it is <quote>reserved.</quote>
    5656       </para>
    5757    </note>
    … …  
    349349
    350350  <para>The <filename>/etc/sysconfig/console</filename> file should contain lines
    351   of the form: VARIABLE="value". The following variables are recognized:</para>
     351  of the form: <envar>VARIABLE=value</envar>. The following variables are recognized:</para>
    352352  <variablelist>
    353353
    … …  
    357357        <para>This variable specifies the log level for kernel messages sent
    358358        to the console as set by <command>dmesg -n</command>. Valid levels are
    359         from "1" (no messages) to "8". The default level is "7".</para>
     359        from <literal>1</literal> (no messages) to <literal>8</literal>. The default level is <literal>7</literal>, which is quite verbose.</para>
    360360      </listitem>
    361361    </varlistentry>
    … …  
    366366        <para>This variable specifies the arguments for the
    367367        <command>loadkeys</command> program, typically, the name of the keymap
    368         to load, e.g., <quote>it</quote>. If this variable is not set, the
     368        to load, e.g., <literal>it</literal>. If this variable is not set, the
    369369        bootscript will not run the <command>loadkeys</command> program,
    370370        and the default kernel keymap will be used.  Note that a few keymaps
    … …  
    385385        is not completely satisfactory and a small adjustment has to be made. E.g.,
    386386        to include the Euro sign into a keymap that normally doesn't have it,
    387         set this variable to <quote>euro2</quote>.</para>
     387        set this variable to <literal>euro2</literal>.</para>
    388388      </listitem>
    389389    </varlistentry>
    … …  
    394394        <para>This variable specifies the arguments for the
    395395        <command>setfont</command> program. Typically, this includes the font
    396         name, <quote>-m</quote>, and the name of the application character
     396        name, <literal>-m</literal>, and the name of the application character
    397397        map to load. E.g., in order to load the <quote>lat1-16</quote> font
    398398        together with the <quote>8859-1</quote> application character map
    399399        (appropriate in the USA),
    400400        <!-- because of the copyright sign -->
    401         set this variable to <quote>lat1-16 -m 8859-1</quote>.
     401        set this variable to <literal>lat1-16 -m 8859-1</literal>.
    402402        In UTF-8 mode, the kernel uses the application character map to
    403403        convert 8-bit key codes to UTF-8. Therefore
    … …  
    411411      <term>UNICODE</term>
    412412      <listitem>
    413         <para>Set this variable to <quote>1</quote>, <quote>yes</quote>, or
    414         <quote>true</quote> in order to put the
     413        <para>Set this variable to <literal>1</literal>, <literal>yes</literal>, or
     414        <literal>true</literal> in order to put the
    415415        console into UTF-8 mode. This is useful in UTF-8 based locales and
    416416        harmful otherwise.</para>
    … …  
    527527      characters, or two ASCII characters are composed together. However, in
    528528      UTF-8 mode it is a problem; e.g., for the Greek language, where one
    529       sometimes needs to put an accent on the letter <quote>alpha</quote>.
     529      sometimes needs to put an accent on the letter <quote>alpha.</quote>
    530530      The solution is either to avoid the use of UTF-8, or to install the
    531531      X window system, which doesn't have this limitation, in its input

  • chapter10/grub.xml

    r44850bb r360fdfca  
    121121    </note>
    122122
    123 <!-- This does not seem to be true any more
    124     <note><para><application>grub-install</application> is a script and calls another
    125     program, grub-probe, that may fail with a message "cannot stat `/dev/root'".
    126     If so, create a temporary symbolic link from your root partition to /dev/root:</para>
    127 
    128 <screen role="nodump"><userinput>ln -sv /dev/sda2 /dev/root</userinput></screen>
    129 
    130     <para>The symbolic link will only be present until the system is rebooted.
    131     The link is only needed for the installation procedure.
    132     </para></note>
    133 -->
    134123  </sect2>
    135124

  • part3intro/toolchaintechnotes.xml

    r44850bb r360fdfca  
    5757      <varlistentry><term>The build</term><listitem>
    5858        <para>is the machine where we build programs. Note that this machine
    59         is also referred to as the <quote>host</quote>.</para></listitem>
     59        is also referred to as the <quote>host.</quote></para></listitem>
    6060      </varlistentry>
    6161

  • prologue/standards.xml

    r44850bb r360fdfca  
    5050
    5151    <para>While it is possible to create a complete system that will pass the LSB
    52     certification tests "from scratch", this can't be done without many additional packages
     52    certification tests <quote>from scratch,</quote> this can't be done without many additional packages
    5353    that are beyond the scope of the LFS book.  Installation instructions for these
    5454    additional packages can be found in BLFS. </para>

  • prologue/typography.xml

    r44850bb r360fdfca  
    8686  specifically referring to <filename>/usr/share/man/man5/passwd.5</filename>.
    8787  <command>man passwd</command> will print the first man page it finds that
    88   matches <quote>passwd</quote>, which will be
     88  matches <quote>passwd,</quote> which will be
    8989  <filename>/usr/share/man/man1/passwd.1</filename>. For this example, you will
    9090  need to run <command>man 5 passwd</command> in order to read the page
Note: See TracChangeset for help on using the changeset viewer.