https://bugs.documentfoundation.org/show_bug.cgi?id=156200

Michael Weghorn <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #20 from Michael Weghorn <[email protected]> ---
(In reply to kde-user from comment #19)
> Addition:
> 
> Until now, the Flatpak version of LibreOffice was the only version left,
> that did NOT have the problem with bad font rendering, when anti-aliasing
> was disabled.
> This has now changed with the update from November 8th, 2023 and the Flatpak
> version is also affected!
> 
> What I found out:
> Flatpaks have so-called commit codes, that can be used to clearly identify a
> version.
> 
> The last NOT affected version was 7.6.2.1 from 10/23/23,
> Commit code 7a83544cc21d1380efb3eeeb9f10adb26d125bc8db4936e82312a96e357e9abf
> 
> The version now affected is (strangely enough) also version 7.6.2.1 from
> November 8th, 2023,
> Commit code 1aa14038cbe7408fab115258b431132b7c0d1e9e257ba194c187a96df5e5be95
> The subject of this version says:
> Replace use of "Calibri" and "Calibri Light" with "Noto Sans" (b6ecbefa)
> 
> But to what extent this is the only change from the previous version, and
> whether or what this change has to do with font rendering in LO Writer, I
> don't know.
> But something must have changed in this version, because immediately when I
> downgrade to the previous version everything is fine again!
> 
> Nobody an idea?

@Stephan: Any idea?

I suppose the mentioned

> > Replace use of "Calibri" and "Calibri Light" with "Noto Sans" (b6ecbefa)

is just the font replacement for unit tests, which should be unrelated.

Not having much experience with Flatpak, one thought that came to my mind:
Besides changes to LibreOffice itself, could this possibly also be related to
some change in Flatpak/the sandboxing mechanism, e.g. if some portal now makes
font settings available for the Flatpak app as well that were previously
ignored there?

>From a quick glance at the changes, there seems to have been a runtime update
[1] which may or may not be relevant if something like this is possible.

[1] https://github.com/flathub/org.libreoffice.LibreOffice/pull/264

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to