Dan Nicholson wrote:
On 2/1/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
#1957 was closed then reopened. If there is discussion necessary,
someone please open a new thread in blfs-dev.
I'd prefer if Alexander took charge on that one, but I certainly
understand if he doesn't have time. I think it's straightforward
enough to just add the warning tags with some text (there's usually
more detail in the Wiki). I'd like to see them go in if possible, even
if the warning just says "This package has problems with locale
issues, see the Wiki."
I have most of the changes sitting in my working copy. The diff is attached.
It remains to add warnings to A2PS and Enscript, and populate the teTeX wiki
page.
--
Alexander E. Patrakov
Index: introduction/important/locale-issues.xml
===================================================================
--- introduction/important/locale-issues.xml (revision 6518)
+++ introduction/important/locale-issues.xml (working copy)
@@ -213,7 +213,7 @@
</sect2>
<sect2 id="locale-wrong-multibyte-characters"
- xreflabel="Wrong Multibyte Characters">
+ xreflabel="Breaks Multibyte Characters">
<title>The Program Breaks Multibyte Characters or Doesn't Count
Character Cells Correctly</title>
Index: basicnet/textweb/links.xml
===================================================================
--- basicnet/textweb/links.xml (revision 6518)
+++ basicnet/textweb/links.xml (working copy)
@@ -33,7 +33,23 @@
WWW browser. It includes support for rendering
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 Locale Related 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>
<itemizedlist spacing="compact">
<listitem>
@@ -132,6 +148,26 @@
files in the <filename class="directory">~/.links</filename> directory.
These
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 > Character set</quote> menu item and
select the character
+ set that matches your locale.</para>
+ </listitem>
+ <listitem>
+ <para>Optionally, go to the <quote>Setup > Language</quote> menu
+ and select the user interface language.</para>
+ </listitem>
+ <listitem>
+ <para>Finally, select the <quote>Setup > Save options</quote>
+ menu item.</para>
+ </listitem>
+ </itemizedlist>
</sect3>
Index: postlfs/editors/ed.xml
===================================================================
--- postlfs/editors/ed.xml (revision 6518)
+++ postlfs/editors/ed.xml (working copy)
@@ -35,6 +35,18 @@
people use. It's described here because it can be used by the patch
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>
<itemizedlist spacing="compact">
Index: postlfs/shells/tcsh.xml
===================================================================
--- postlfs/shells/tcsh.xml (revision 6518)
+++ postlfs/shells/tcsh.xml (working copy)
@@ -35,6 +35,13 @@
for those who prefer C syntax to that of the <command>bash</command> shell,
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>
<itemizedlist spacing="compact">
Index: postlfs/shells/ash.xml
===================================================================
--- postlfs/shells/ash.xml (revision 6518)
+++ postlfs/shells/ash.xml (working copy)
@@ -38,6 +38,13 @@
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>
<itemizedlist spacing="compact">
<listitem>
Index: xsoft/graphweb/dillo.xml
===================================================================
--- xsoft/graphweb/dillo.xml (revision 6518)
+++ xsoft/graphweb/dillo.xml (working copy)
@@ -37,6 +37,12 @@
fast and so is useful on older, slower machines. It supports downloads
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">
<listitem>
@@ -80,12 +86,6 @@
<sect2 role="installation">
<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
<application>Dillo</application>'s author. If you want the optional HTTPS
Index: general/sysutils/mc.xml
===================================================================
--- general/sysutils/mc.xml (revision 6518)
+++ general/sysutils/mc.xml (working copy)
@@ -76,7 +76,8 @@
content corruption similar to what is depicted in
<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
<command>mcedit</command>, and improved syntax highlighting.</para>
Index: general/sysutils/unzip.xml
===================================================================
--- general/sysutils/unzip.xml (revision 6518)
+++ general/sysutils/unzip.xml (working copy)
@@ -42,7 +42,9 @@
<para>The <application>UnZip</application> package has some locale
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>
Index: general/genlib/glib2.xml
===================================================================
--- general/genlib/glib2.xml (revision 6518)
+++ general/genlib/glib2.xml (working copy)
@@ -102,6 +102,7 @@
<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
that filenames are in the default locale encoding, set the variable
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
