Bug#584801: problem with German umlaut

2010-06-09 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/10 02:18, pac...@kosh.dhis.org wrote: The root of the problem is that in non-UTF-8 mode, the \x9f character eats an arbitrarily large sequence of non-control characters that follow it. On 06/08/10 02:24, Thomas Dickey wrote:

Bug#584801: problem with German umlaut

2010-06-09 Thread Thomas Dickey
On Wed, 9 Jun 2010, Harald Dunkel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/10 02:18, pac...@kosh.dhis.org wrote: The root of the problem is that in non-UTF-8 mode, the \x9f character eats an arbitrarily large sequence of non-control characters that follow it. On

Bug#584801: problem with German umlaut

2010-06-09 Thread Thomas Dickey
On Wed, 9 Jun 2010, Harald Dunkel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/10 02:18, pac...@kosh.dhis.org wrote: The root of the problem is that in non-UTF-8 mode, the \x9f character eats an arbitrarily large sequence of non-control characters that follow it. On

Bug#584801: problem with German umlaut

2010-06-09 Thread pacman
Harald Dunkel writes: Is this a special xterm feature? whois sensors.de works much better with -k8. Would you suggest to make -k8 the default? In a perfect world, it would be unnecessary since you wouldn't have anything written on your terminal that wasn't in the proper charset. In the real

Bug#584801: problem with German umlaut

2010-06-09 Thread Thomas Dickey
On Wed, 9 Jun 2010, pac...@kosh.dhis.org wrote: Harald Dunkel writes: Is this a special xterm feature? whois sensors.de works much better with -k8. Would you suggest to make -k8 the default? In a perfect world, it would be unnecessary since you wouldn't have anything written on your

Bug#584801: problem with German umlaut

2010-06-07 Thread pacman
Thomas Dickey writes: That file is all ascii, so probably not what you wanted to attach. ascii here, too. That must be some kind of mail system bug, closer to your end than the submitter. Viewing on http://bugs.debian.org/584801 I can see that the original message included this

Bug#584801: problem with German umlaut

2010-06-07 Thread Thomas Dickey
On Mon, 7 Jun 2010, pac...@kosh.dhis.org wrote: The root of the problem is that in non-UTF-8 mode, the \x9f character eats an arbitrarily large sequence of non-control characters that follow it. http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#C1

Bug#584801: problem with German umlaut

2010-06-06 Thread Harald Dunkel
Package: xterm Version: 258-1 If I switch off UTF-8 mode and do 'cat strasse.txt' (attached) in bash, then the text is cut off at the German umlaut. 'xterm -e tail -f strasse.txt' shows the same problem. Using /bin/sh (a symlink to dash) the shell even gets stuck (which us a severe problem).

Bug#584801: problem with German umlaut

2010-06-06 Thread Julien Cristau
On Sun, Jun 6, 2010 at 20:02:16 +0200, Harald Dunkel wrote: Package: xterm Version: 258-1 If I switch off UTF-8 mode and do 'cat strasse.txt' (attached) in bash, then the text is cut off at the German umlaut. 'xterm -e tail -f strasse.txt' shows the same problem. Using /bin/sh (a symlink

Bug#584801: problem with German umlaut

2010-06-06 Thread Thomas Dickey
On Sun, Jun 06, 2010 at 08:17:39PM +0200, Julien Cristau wrote: On Sun, Jun 6, 2010 at 20:02:16 +0200, Harald Dunkel wrote: Package: xterm Version: 258-1 If I switch off UTF-8 mode and do 'cat strasse.txt' (attached) in bash, then the text is cut off at the German umlaut. 'xterm -e