Bug#1089108: /usr/bin/gnome-terminal: wrongly displays unicode sequences involving combining characters

Uwe Kleine-König ukleinek at debian.org
Thu Dec 5 18:41:49 GMT 2024


Hello Simon,

thanks for your quick reply.

On 12/5/24 19:28, Simon McVittie wrote:
> Control: tags -1 + moreinfo
> 
> On Thu, 05 Dec 2024 at 19:05:16 +0100, Uwe Kleine-König wrote:
>> The (e.g.) combining Acute Accent (codepoint 0x301, utf-8 representation
>> "\xcc\x81") is supposed to put an accent on the char just before it.
>>
>> That is
>>
>> 	echo -e "e\xcc\x81e" | iconv -f utf-8
>>
>> is supposed to show two e with the first having an accent.
> 
> This works as you say it should for me, in gnome-terminal and kgx
> (gnome-console).

kgx gets it right for me, too.

> What byte sequence is output from iconv on your system?
> (echo -e "e\xcc\x81e" | iconv -f utf-8 | xxd)
> 
> I expect that the answer should be:
> 
> 00000000: 65cc 8165 0a                             e..e.

Indeed. I only added the iconv in case someone wants to reproduce with a 
non-utf-8 encoding.

> which is U+0065 'e', U+0301 combining acute accent, U+0065 'e', newline.
> 
>> ii  libpango-1.0-0                                1.54.0+ds-3
> 
> I have version 1.55.0+ds-3, if that matters.
> 
>> ii  libvte-2.91-0                                 0.78.1-1
> 
> I have version 0.78.2-1, if that matters.

I updated these two to the version you have (i.e. current unstable) and 
the problem persists in gnome-terminal (even after a reboot).
Then maybe a transitive dependency is the culprit???

Best regards
Uwe



More information about the pkg-gnome-maintainers mailing list