Changeset 864b24de for introduction

Timestamp:

01/16/2007 12:08:14 AM (17 years ago)

Author:

Randy McMurchy <randy@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.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/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

4e88613

Parents:

15b3bc29

Message:

Removed extraneous spaces in the XML

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

File:

• introduction/important/locale-issues.xml (modified) (6 diffs)

introduction/important/locale-issues.xml

@@ -113 +113 @@
     details.</para>
 
-    <para>In extreme cases, Windows encoding compatibility issues may be 
+    <para>In extreme cases, Windows encoding compatibility issues may be
     solved only by running Windows programs under
     <ulink url="http://www.winehq.com/">Wine</ulink>.</para>
@@ -130 +130 @@
     information is well-hidden on the page which specifies the behavior
     of <application>Tar</application> and <application>Cpio</application>
-    programs. Some programs get it wrong by default (or simply don't 
+    programs. Some programs get it wrong by default (or simply don't
     have enough information to get it right). The result is that they
     create filenames which are not subsequently shown correctly by
@@ -159 +159 @@
     only correct in UTF-8 locales.</para>
 
-    <para>The general rule for avoiding this class of problems is to 
+    <para>The general rule for avoiding this class of problems is to
     avoid installing broken programs. If this is impossible, the
     <ulink url="http://j3e.de/linux/convmv/">convmv</ulink>
@@ -169 +169 @@
     filenames from a system using a different locale with a tool that
     is not locale-aware (e.g., <xref linkend="nfs-utils"/> or
-    <xref linkend="openssh"/>). In order to avoid mangling non-ASCII 
+    <xref linkend="openssh"/>). In order to avoid mangling non-ASCII
     characters when transferring files to a system with a different
     locale, any of the following methods can be used:</para>
@@ -179 +179 @@
       </listitem>
       <listitem>
-        <para>On the sending side, create a tar archive with the 
+        <para>On the sending side, create a tar archive with the
         <parameter>--format=posix</parameter> switch passed to
-        <command>tar</command> (this will be the default in a future 
+        <command>tar</command> (this will be the default in a future
         version of <command>tar</command>).</para>
       </listitem>
@@ -230 +230 @@
     screen into a complete mess.</para>
 
-    <para>Fixing this kind of problems is a tedious task from a 
-    programmer's point of view, like all other cases of retrofitting new 
-    concepts into the old flawed design. In this case, one has to redesign 
-    all data structures in order to accommodate to the fact that a complete 
-    character may span a variable number of "char"s (or switch to wchar_t 
-    and convert as needed). Also, for every call to the "strlen" and 
-    similar functions, find out whether a number of bytes, a number of 
-    characters, or the width of the string was really meant. Sometimes it 
+    <para>Fixing this kind of problems is a tedious task from a
+    programmer's point of view, like all other cases of retrofitting new
+    concepts into the old flawed design. In this case, one has to redesign
+    all data structures in order to accommodate to the fact that a complete
+    character may span a variable number of "char"s (or switch to wchar_t
+    and convert as needed). Also, for every call to the "strlen" and
+    similar functions, find out whether a number of bytes, a number of
+    characters, or the width of the string was really meant. Sometimes it
     is faster to write a program with the same functionality from scratch.
     </para>