November 2019 - fonts-bugs - Fedora Mailing-Lists

[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 #20 from Alan <alan.g12r(a)outlook.com> --- (In reply to Vendula Poncova from comment #16) > When I install bpg-dejavu-sans-fonts in Live OS, the issue seems to be fixed > (see the attachment F32 Live Screenshot). Could someone confirm that this is > the expected output? If yes, we need to make sure that the font is installed > in the boot.iso (handled by lorax) and Live images (handled by > spin-kickstarts). Anaconda doesn't install any fonts. The text on the right top corner (Fedora's installation) is correctly shown in Georgian, as long as it's all caps. But the word "Georgian" in the language menu is inaccurate, because titlecasing is not expected in modern Georgian. (In reply to Mike FABIAN from comment #9) > So anaconda should make an exception for Georgian not to automatically > capitalize the first letter. Yes, automatic capitalization just should not be applied to Georgian text. A localizer can decide, whether or not to use uppercase for emphasis. > (In reply to Jens Petersen from comment #6) > > It is surprising then that neither bpg-sans-fonts or > > google-noto-sans-georgian-fonts cover the glyph(s). > > There is a work around for Noto fonts: > https://github.com/googlefonts/noto-fonts/issues/1261 > Here you can get bpg-fonts that support Mtavruli: > https://bpgfonts.wordpress.com/2018/09/07/gnu-gpl-license-grant-to-linux- > distributors/ Now Google Noto fonts also include Mtavruli characters (updated 2 months ago): https://github.com/googlefonts/noto-fonts/tree/master/hinted/NotoSansGeor... -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[Bug 1545149] OTF/CFF conts no longer hinted horizontally

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1545149 Pierre Ossman <ossman(a)cendio.se> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|29 |31 --- Comment #30 from Pierre Ossman <ossman(a)cendio.se> --- I haven't seen any indication that this option has been enabled in the Fedora package, so moving to Fedora 31. -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[Bug 1748495] The terminus font is no longer found by gvim, so text files come up with glyphs instead of characters.

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #21 from Mike Pittaro <fedora(a)lahondaresearch.org> --- (In reply to Jan Pazdziora from comment #12) > For people looking for quick relief, I've now rebuilt terminus-fonts using > the fonttosfnt approach from bug 1753295 comment 4 into > https://copr.fedorainfracloud.org/coprs/adelton/fedora-fixes/. Karma! Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[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

1
0
0 / 0

[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 #19 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Yes, sure, it’s bigger than a font or Anaconda, it’s how Georgian is expected to behave, and how it got standardised -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[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

1
0
0 / 0

[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 #17 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[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 #16 from Vendula Poncova <vponcova(a)redhat.com> --- When I install bpg-dejavu-sans-fonts in Live OS, the issue seems to be fixed (see the attachment F32 Live Screenshot). Could someone confirm that this is the expected output? If yes, we need to make sure that the font is installed in the boot.iso (handled by lorax) and Live images (handled by spin-kickstarts). Anaconda doesn't install any fonts. -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[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 #15 from Vendula Poncova <vponcova(a)redhat.com> --- Created attachment 1635300 --> https://bugzilla.redhat.com/attachment.cgi?id=1635300&action=edit F32 Live Screenshot -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

[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 #14 from Jiri Konecny <jkonecny(a)redhat.com> --- 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... -- You are receiving this mail because: You are on the CC list for the bug.

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs November 2019