Mail Archives: geda-help/2020/09/02/18:00:48
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323329-337776202-1599083118=:1252
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT
On Wed, Sep 02, 2020 at 10:48:31AM -0400, Glen W. Ruch (gw DOT ruch AT yahoo DOT com)
[via geda-help AT delorie DOT com] wrote:
> [ruchg AT localhost ~]$ dnf list installed | grep pango
> […] 1.44.7-2.fc32 […]
I see. From version 1.44 on, Pango switched from FreeType to HarfBuzz for
font rendering, which is causing a lot of issues. I assume this is one of
them.
> If you want me to compile, it will take me some time to find the source
> and download.?? - - - assuming I find all the dependencies etc.
This would be really helpful. Debian has `apt-get build-dep geda-gaf' to
install all build dependencies for geda-gaf; I assume Fedora has a similar
feature. I can't reproduce the bug on my machine, so I need feedback from
someone who can in order to see if the metric cache is actually what's
causing the issue.
On Wed, 2 Sep 2020, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via
geda-help AT delorie DOT com] wrote:
> The rendering issues have been introduced in the new version of
> Pango---1.44. We've have been already fixed many of them in Lepton
> 1.9.11 (Lepton is a fork of 'geda-gaf').
I had a look at these fixes. If I understand it correctly, you ditched
baseline alignment completely and use the "logical" text boundaries for
text alignment which introduces a large gap between the text and the
anchor point for both "lower" and "upper" alignment.
As a rationale, you wrote in the commit message that "the
'pango_font_metrics*()' functions […] were considered unstable and we used
them at our own risk". Do you have any reference for this?
--8323329-337776202-1599083118=:1252--
- Raw text -