[Fedora-i18n-bugs] [Bug 1762455] IBUS input methods don't work in QT5-based applications
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
Michael Catanzaro <mcatanzaro(a)gnome.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mcatanzaro(a)gnome.org
Flags|needinfo?(mclasen(a)redhat.co |
|m) |
--- Comment #11 from Michael Catanzaro <mcatanzaro(a)gnome.org> ---
Due to scheduling, we decided to wait a few days for glib 2.62.3 before
preparing a F31 update. Please make sure to reopen this bug if bodhi closes it
if the F30 update lands before the F31 update is ready.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 5 months
[Fedora-i18n-bugs] [Bug 1090631] Please set TT_NAME_ID_PREFERRED_FAMILY for Liberation fonts
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
--- Comment #9 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
TT_NAME_ID_FONT_FAMILY (Name ID 16) is actually quite problematic, it was not
defined strictly enough to be useful for apps.
The correct way to group fonts is to use Name ID 21, and fallback to Name ID 16
if it is not present. Though Name ID 21 may be absent either because 16 already
has the value 21 would have, or because 16 is completely broken but not yet
fixed via 21.
Distinguishing between those two cases requires setting bit 8 of the
fsSelection correctly (and reading this bit app-side)
https://docs.microsoft.com/en-us/typography/opentype/spec/name
In any case keying "Liberation" is *definitely* broken from a OpenType WWS PoW,
so using it in Liberation files *requires* setting Name ID 21 to fix it.
If fail to see the point of introducing known-broken naming at the 16 layer,
just to get the benefit to fix it at the 21 layer. Just use WWS-conformant
naming at 16 and 17 directly.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 5 months
[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #18 from Jiri Konecny <jkonecny(a)redhat.com> ---
(In reply to Nicolas Mailhot from comment #17)
> (In reply to Jiri Konecny from comment #14)
> > The question is if we should use other fonts which would work or to change
> > Anaconda code. Honestly the first variant seems like a less hacky to me...
>
> The first option is a short-term workaround. The way Georgian has been
> standardized Unicode-side is not expected to change. So if anaconda does not
> handle it properly, the issue will come back in a few releases when the
> Fedora font set gets updated.
Don't you think that this problem is bigger than Anaconda? Anaconda is just one
of the projects but all the projects supporting Georgian may experience the
same issue. I don't think it's reasonable to fix one case instead of fixing the
root cause here.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 5 months