GNU bug report logs - #44664
28.0.50; troubles with some chars in term

Previous Next

Full log

View this message in rfc822 format

From: Jean Louis <bugs <at> gnu.support>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Andreas Schwab <schwab <at> linux-m68k.org>, 44664 <at> debbugs.gnu.org
Subject: bug#44664: 28.0.50; troubles with some chars in term
Date: Wed, 18 Nov 2020 09:05:42 +0300

* Eli Zaretskii <eliz <at> gnu.org> [2020-11-18 06:31]:
> > From: Andreas Schwab <schwab <at> linux-m68k.org>
> > Cc: Jean Louis <bugs <at> gnu.support>,  44664 <at> debbugs.gnu.org
> > Date: Tue, 17 Nov 2020 23:02:28 +0100
> > 
> > On Nov 17 2020, Eli Zaretskii wrote:
> > 
> > >> Date: Tue, 17 Nov 2020 20:15:01 +0300
> > >> From: Jean Louis <bugs <at> gnu.support>
> > >> Cc: schwab <at> linux-m68k.org, 44664 <at> debbugs.gnu.org
> > >> 
> > >> > That depends on the characters you need to display.  Which characters
> > >> > look bad/corrupted in term?  What are their codepoints?
> > >> 
> > >> �θ��� ���µ� �ƴѵ� 5���� ������??..............................
> > >
> > > Most of those didn't make it, please show their codepoints instead.
> > 
> > Thats's the result of mutt trying to interpret (undeclared) BIG5 as
> > UTF-8.
> 
> In which case it is not a font problem, it is a problem with
> undeclared encoding of a mail message.  And the characters aren't
> corrupted on display, they are just shown as octal escapes.

In any other terminal mutt is handling that well and terminal does not
make me any problems.

To avoid problems I am often using emacs-libvterm dynamic module.

ansi-term and term do not work with such.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.