GNU bug report logs - #73752
29.4; Ligatures are randomly rendered with extra spaces

Previous Next

Full log

Message #263 received at 73752 <at> debbugs.gnu.org (full text, mbox):

From: Visuwesh <visuweshm <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: dev <at> real-or-random.org, xuan <at> xlk.me, mituharu <at> math.s.chiba-u.ac.jp,
 73752 <at> debbugs.gnu.org
Subject: Re: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces
Date: Thu, 07 Nov 2024 20:43:32 +0530

On 7 November 2024 20:10:49 GMT+05:30, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> From: Visuwesh <visuweshm <at> gmail.com>
>> Cc: Tim Ruffing <dev <at> real-or-random.org>,  mituharu <at> math.s.chiba-u.ac.jp,
>>   xuan <at> xlk.me,  73752 <at> debbugs.gnu.org
>> Date: Thu, 07 Nov 2024 19:15:30 +0530
>> 
>> [வியாழன் நவம்பர் 07, 2024] Eli Zaretskii wrote:
>> 
>> >> From: Tim Ruffing <dev <at> real-or-random.org>
>> >> Cc: mituharu <at> math.s.chiba-u.ac.jp, visuweshm <at> gmail.com, xuan <at> xlk.me, 
>> >> 	73752 <at> debbugs.gnu.org
>> >> Date: Thu, 07 Nov 2024 03:12:19 +0100
>> >> 
>> >> On Wed, 2024-11-06 at 15:11 +0200, Eli Zaretskii wrote:
>> >> > 
>> >> > 
>> >> > Thanks.  Can you try calling hb_font_destroy in
>> >> > ftcrhbfont_end_hb_font
>> >> > and setting ftcrfont_info->hb_font to NULL right after that?  If that
>> >> > solves the problem, we could at least install this for now, until we
>> >> > have a better solution (if one exists).
>> >> 
>> >> Yes, that appears to work. And I don't think there's an obvious better
>> >> solution. See attached patch.
>> >
>> > Thanks.  Visuwesh, does this patch fix your problem as well?
>> 
>> I cannot reproduce the original issue but it leads to following
>> backtrace when I visit dinamalar.com in eww, and click on any of the
>> links coloured in blue: say the one under the heading named "வாராவாரம்".
>> Directly visiting a link doesn't produce the backtrace though.  I need
>> to visit a webpage with Tamil text on it twice to trigger it.  It might
>> well be a false warning since I see the warning
>> 
>>     Warning: program compiled against libxml 212 using older 209
>>     Warning: program compiled against libxml 212 using older 209
>> 
>> in stderr printed.  I updated my system (kernel updates included) but
>> haven't restarted it yet.  Of course, I built Emacs _after_ the update.
>> If you want me to restart and check if you believe it is a false
>> warning, I am to do so.  Maybe a `make bootstrap' or somesuch is also in
>> order?
>
>This abort is unrelated: I also get it, with no changes at all, and
>also in Emacs 30.  It looks like we fail to decode the text there, and
>a buffer ends up with an invalid byte sequence, which triggers an
>assertion violation.  Please open a separate bug report about that.

Okay will do so.

>As for this bug, I will install the patch soon, 

I would dare to merge bug#54646 with this when you close the bug since I'm confident they both have the same underlying cause.

>thanks to all for the efforts to investigate this tricky bug.

Thank you very much Tim for your investigation!  This was a paper cut that annoyed me to no end when I was viewing composed Tamil text which forced me to abandon reading Tamil text altogether inside Emacs.

Previous Next

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