Changeset a4b9cd7

Timestamp:

02/02/2007 11:00:08 AM (17 years ago)

Author:

Alexander E. Patrakov <alexander@…>

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-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:

b7bb66d

Parents:

4972971

Message:

Added caution boxes for packages that are not going to work in UTF-8 locales
Added CUPS and LPRng as recommended a2ps dependencies
Replaced some tabs with spaces

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

Files:

• basicnet/textweb/links.xml (modified) (2 diffs)
• general/genlib/glib2.xml (modified) (1 diff)
• general/sysutils/mc.xml (modified) (1 diff)
• general/sysutils/unzip.xml (modified) (1 diff)
• introduction/important/locale-issues.xml (modified) (1 diff)
• introduction/welcome/changelog.xml (modified) (3 diffs)
• postlfs/editors/ed.xml (modified) (1 diff)
• postlfs/filesystems/xfs.xml (modified) (1 diff)
• postlfs/shells/ash.xml (modified) (1 diff)
• postlfs/shells/tcsh.xml (modified) (1 diff)
• pst/ps/a2ps.xml (modified) (2 diffs)
• pst/ps/enscript.xml (modified) (1 diff)
• xsoft/graphweb/dillo.xml (modified) (2 diffs)

basicnet/textweb/links.xml

@@ -34 +34 @@
     tables and frames, features background downloads, can display colors
     and has many other features.</para>
+    
+    <caution>
+      <para>In the text mode, <application>Links</application> cannot be
+      configured to use UTF-8 encoding for the terminal output. This
+      limitation renders <application>Links</application> useless as a
+      text-based browser in UTF-8 locales. See general discussion of this
+      type of issue in the <xref linkend="locale-not-valid-option"/> section
+      on the <xref linkend="locale-issues"/> page.</para>
+
+      <para>In the graphical mode,
+      <application>Links</application> displays text correctly even in
+      UTF-8 locales, if all characters exist in the built-in font used by
+      <application>Links</application>. Form submission in UTF-8 locales
+      is handled correctly when running in X11-based (but not framebuffer-based)
+      graphical mode.</para>
+    </caution>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -133 +149 @@
       files are created automatically when <command>links</command> is run for the
       first time.</para>
+      
+      <para>For the correct display of non-ASCII characters, <application>Links</application>
+      has to be configured through the menu (accessible by pressing the ESC key),
+      as follows:</para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>If running <application>Links</application> in the text mode,
+          go to the <quote>Setup &gt; Character set</quote> menu item and select the character
+          set that matches your locale.</para>
+        </listitem>
+        <listitem>
+          <para>Optionally, go to the <quote>Setup &gt; Language</quote> menu
+          and select the user interface language.</para>
+        </listitem>
+        <listitem>
+          <para>Finally, select the <quote>Setup &gt; Save options</quote>
+          menu item.</para>
+        </listitem>
+      </itemizedlist>
 
     </sect3>

general/genlib/glib2.xml

@@ -103 +103 @@
       <para>By default, <application>GLib</application> assumes that all
       filenames are in the UTF-8 charset. See the <xref
+      linkend="locale-wrong-filename-encoding"/> section of the <xref
       linkend="locale-issues"/> page for more details on this kind of
       issue. In order to tell GLib and applications that use it

general/sysutils/mc.xml

@@ -77 +77 @@
     <ulink url="&files-anduin;/mc-bad.png">this screenshot</ulink>
     (taken in the ru_RU.UTF-8 locale). For a general discussion of this type
-    of issue, see the <xref linkend="locale-issues"/> page. The Debian patch
+    of issue, see the <xref linkend="locale-wrong-multibyte-characters"/>
+    section of the <xref linkend="locale-issues"/> page. The Debian patch
     mostly fixes this issue, and adds support for recoding remote FTP
     filenames. Debian also fixed 64-bit issues, rare segfaults in

general/sysutils/unzip.xml

@@ -43 +43 @@
       related issues. See the discussion below in
       <xref linkend="unzip-locale-issues"/>. A more general
-      discussion of these problems can be found on the
+      discussion of these problems can be found in the
+      <xref linkend="locale-assumed-encoding"/>
+      section of the
       <xref linkend="locale-issues"/> page.</para>
     </caution>

introduction/important/locale-issues.xml

@@ -214 +214 @@
 
   <sect2 id="locale-wrong-multibyte-characters"
-         xreflabel="Wrong Multibyte Characters">
+         xreflabel="Breaks Multibyte Characters">
 
     <title>The Program Breaks Multibyte Characters or Doesn't Count

introduction/welcome/changelog.xml

@@ -46 +46 @@
       <itemizedlist>
         <listitem>
+          <para>[alexander] - Added CUPS and LPRng as recommended dependencies
+          of a2ps.</para>
+        </listitem>
+        <listitem>
+          <para>[alexander] - Added some caution boxes for packages that
+          are not going to work in multibyte locales.</para>
+        </listitem>
+        <listitem>
           <para>[bdubbs] - Updated to Koffice-1.6.1.</para>
         </listitem>
@@ -94 +102 @@
           Preface.</para>
         </listitem>
-        <listitem>
+        <listitem>
           <para>[alexander] - Upgraded GC to version 6.8 in order to fix the
           build failure with GCC-4.1.1.</para>
@@ -433 +441 @@
         <listitem>
           <para>[alexander] - Updated to xfsprogs-2.8.18, added notes about
-          the lack of testsuites to xfsprogs and reiserfsprogs.</para>
+          the lack of testsuites to xfsprogs and reiserfsprogs.</para>
         </listitem>
       </itemizedlist>

postlfs/editors/ed.xml

@@ -36 +36 @@
     program if you encounter an ed-based patch file. This happens rarely
     because diff-based patches are preferred these days.</para>
+    
+    <caution>
+      <para><application>Ed</application> determines character boundaries
+      incorrectly in multibyte locales. See the
+      <xref linkend="locale-wrong-multibyte-characters"/>
+      section of the <xref linkend="locale-issues"/> page for a more
+      general discussion of this problem. Use of <application>Ed</application>
+      in installation instructions for BLFS packages such as
+      <xref linkend="tetex"/> is not a problem, as BLFS instructions never
+      use <application>Ed</application> to modify a file containing
+      non-ASCII characters.</para>
+    </caution>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>

postlfs/filesystems/xfs.xml

@@ -325 +325 @@
         <listitem>
           <para>contains XFS-specific functions that provide a way to perform
-          certain filesystem  operations without using a file descriptor to
-          access filesystem objects.</para>
+          certain filesystem  operations without using a file descriptor to
+          access filesystem objects.</para>
           <indexterm zone="xfs libhandle">
             <primary sortas="c-libhandle">libhandle.so</primary>

postlfs/shells/ash.xml

@@ -38 +38 @@
     requirements compared to the other <command>sh</command>-compliant
     shells.</para>
+
+    <caution>
+      <para><application>Ash</application> has problems with command line
+      editing in multibyte locales. The issue is discussed in more detail
+      in the <xref linkend="locale-wrong-multibyte-characters"/> section
+      of the <xref linkend="locale-issues"/> page.</para>
+    </caution>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>

postlfs/shells/tcsh.xml

@@ -36 +36 @@
     and also because some programs require the C shell in order to perform
     installation tasks.</para>
+    
+    <caution>
+      <para><application>Tcsh</application> has problems with command line
+      editing in multibyte locales. The issue is discussed in more detail
+      in the <xref linkend="locale-wrong-multibyte-characters"/> section
+      of the <xref linkend="locale-issues"/> page.</para>
+    </caution>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>

pst/ps/a2ps.xml

@@ -34 +34 @@
     every input format into PostScript output. The application's name
     expands appropriately to "all to PostScript".</para>
+    
+    <caution>
+      <para><application>a2ps</application> cannot convert UTF-8 encoded
+      text to PostScript. The issue is discussed in detail in the
+      <xref linkend="locale-not-valid-option"/> section of the
+      <xref linkend="locale-issues"/> page.
+      The solution is to use <xref linkend="paps"/>, instead of
+      <application>a2ps</application>, for converting
+      UTF-8 encoded text to PostScript.</para>
+    </caution>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -66 +76 @@
 
     <bridgehead renderas="sect3">a2ps Dependencies</bridgehead>
+
+    <bridgehead renderas="sect4">Recommended</bridgehead>
+    <para role="recommended"><xref linkend="cups"/> or <xref linkend="LPRng"/>
+    (otherwise, <application>a2ps</application> will use the
+    <command>cat &gt;/dev/lp0</command> command instead of <command>lpr</command>
+    for sending its output to the printer)</para>
 
     <bridgehead renderas="sect4">Optional</bridgehead>

pst/ps/enscript.xml

@@ -36 +36 @@
     <para><application>Enscript</application> converts ASCII text files
     to PostScript, HTML, RTF, ANSI and overstrikes.</para>
+
+    <caution>
+      <para><application>Enscript</application> cannot convert UTF-8 encoded
+      text to PostScript. The issue is discussed in detail in the
+      <xref linkend="locale-not-valid-option"/> section of the
+      <xref linkend="locale-issues"/> page.
+      The solution is to use <xref linkend="paps"/>, instead of
+      <application>Enscript</application>, for converting
+      UTF-8 encoded text to PostScript.</para>
+    </caution>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>

xsoft/graphweb/dillo.xml

@@ -38 +38 @@
     and can support cookies.</para>
 
+    <caution>
+      <para><application>Dillo</application> always interprets web pages
+      as if they had the ISO-8859-1 encoding. Thus, it is useless
+      for reading non-English web pages.</para>
+    </caution>
+
     <bridgehead renderas="sect3">Package Information</bridgehead>
     <itemizedlist spacing="compact">
@@ -81 +87 @@
     <title>Installation of Dillo</title>
 
-    <note>
-      <para>Dillo has no mechanism of character set selection and always
-      uses iso8859-1. If this character set is not appropriate, replace
-      all occurrences of iso8859-1 to the desired character set in
-      <filename>src/dw_style.c</filename>.</para>
-    </note>
 
     <para>Support for secure connections is considered experimental by