Package: joe
Version: 3.5-1.1
Severity: normal

I've reverted back to Joe 3.5-1.1, because with 3.5-2 there was a
regression regarding charset/encoding detection.

Having still a few non-UTF8 text files over, I'm using the joerc
option -guess_non_utf8. I didn't notice till now, but this feature
has been working exceptionally well.
With 3.5-2 it stopped.

When opening a file in ISO-8859-1, joe 3.5-2 now assumes it was UTF-8
from environment vars or the current locale. Its previous sanity check
does no longer work. (And as far as I tested, the actual char/encoding
of a file cannot be set via commandline arguments or LC_* vars any
longer either.)

The regression stems from one of the recent patches, probably. I've
tracked it down to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408562
##
+  * Fixed CHARSET detection to use the fine system function rather than
+    internal workaround, noticed by Chris Brown, closes: #408562.
##
The "undef HAVE_SETLOCALE" was obviously necessary to provide the
joe option -guess_non_utf8. The system/libc setlocale or whatever,
breaks this feature for me. (Not verified on other setups. But I
believe I have a fairly standard one.)


So, of course, I'd prefer a reversal of that patch.
I also think the previous reporters bug #408562 might have been
mitigated by the alternative option "-guess_utf8" instead.


(PS: Maybe _this_ report is connected to #453310)

-- System Information:
Debian Release: lenny/sid
 APT prefers intrepid-updates
 APT policy: (500, 'intrepid-updates'), (500, 'intrepid-security'),
(500, 'intrepid')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-7-generic (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages joe depends on:
ii  libc6              2.8~20080505-0ubuntu7 GNU C Library: Shared libraries
ii  libncurses5        5.6+20071124-1ubuntu2 Shared libraries for terminal hand

joe recommends no packages.

-- debconf-show failed



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to