[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25288: 25.1; term, ansi-term, broken output of utf8 text
From: |
npostavs |
Subject: |
bug#25288: 25.1; term, ansi-term, broken output of utf8 text |
Date: |
Wed, 28 Dec 2016 21:37:19 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
tags 25288 patch
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: npostavs@users.sourceforge.net
>> Date: Wed, 28 Dec 2016 14:10:30 -0500
>> Cc: 25288@debbugs.gnu.org
>>
>> Is there a way to recognize incomplete decoding from lisp? I can't see
>> any.
>
> If you know the encoding of the byte stream (and term.el must, since
> it evidently decodes it later on), then you could probably use
> char-charset, after decoding: if you get 'eight-bit, then you've got
> incomplete byte sequence. But I didn't try that.
That should work at least for encodings like utf-8 for which undecoded
bytes are not ascii. I guess parsing of escape codes would only work on
such encodings anyway, so it should be fine. Patch attached.
v1-0001-Handle-multibyte-chars-spanning-chunks-in-term.el.patch
Description: patch