fonts-bugs May 2020

fonts-bugs@lists.fedoraproject.org

1 participants
109 discussions

[Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #20 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691590 --> https://bugzilla.redhat.com/attachment.cgi?id=1691590&action=edit Italics font broken in GTK font selection dialog (lxappearance) This might be redundant and more related to Bug 1827905, but I figured I'd mention it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #19 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691589 --> https://bugzilla.redhat.com/attachment.cgi?id=1691589&action=edit Firefox (and HexChat) seem to handle the font better, and aren't broken. Learning why these applications aren't completely broken could be useful in finding a temporary workaround (even if it would be on a per-application basis). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #18 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691588 --> https://bugzilla.redhat.com/attachment.cgi?id=1691588&action=edit GTK apps are broken This is noteworthy because, although only the italics version of the font seems to be glyphs/boxes, a lot of GTK applications are unable to correctly display the font. This also affects Eclipse and many Gnome applications. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Andrew Obuchowicz <aobuchow(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aobuchow(a)redhat.com --- Comment #17 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- I've encountered this issue recently after updating to F32 from F30. Is there a suggested workaround? I really would like to continue using Terminus as my system font, and the Terminus TTF font is blurry :( Some additional notes: - Despite the fact that only the Italic version of Terminus is broken in my font selection dialog (using lxappearance), GTK apps such as the Gnome file manager and Eclipse are completely broken when Terminus is used as the system font. Only glyphs appear. - Certain GTK applications don't seem to break (such as Firefox and HexChat). They seem to handle this bug better? If someone could find out what these applications are doing better, then other applications could make a workaround update until the core issue is resolved. I work on Eclipse IDE and would be willing to try and get this workaround into Eclipse. - Removing all *.pcf.gz fonts didn't seem to fix the issue for me, and worst, it broke the Terminus font for KDE Plasma. - QT (or more specifically, KDE) applications seem to be handling this better. All my KDE apps still look fine, and the font selection dialog does not suggest the italics version of Terminus, and labels it Terminus [xos4]. I'll attach some related screenshots. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #36 from Alan <alan.g12r(a)outlook.com> --- Yeah, it's based on Latin proportions. Maybe this type of fonts are more compatible for mobile screens. https://i.imgur.com/Qb8rFah.png Besarion has made a comparison of them here: https://bpgfonts.wordpress.com/2009/01/31/%E1%83%9E%E1%83%A0%E1%83%9D%E1%83… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #35 from George Machitidze <giomac(a)gmail.com> --- Good, that's Akaki But font is large: https://drive.google.com/file/d/1rUsmuLRyLCqfenjFMsc73SPe-ZBfSv-C/view?usp=… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #34 from Alan <alan.g12r(a)outlook.com> --- @George Machitidze The author of Google Noto Georgian is Akaki Razmadze. More info - https://www.marketer.ge/akaki-razmadze-ios13-android-10/ He also designed FiraGO Georgian, which is publicly available under FOSS license. So, I think, you can feel free to contact him. It's a modern-style typeface. Please see Besarion's post on FB https://www.facebook.com/groups/geotypography/permalink/1499502893517216/?c… Yes, I know who you are (from Tbilisi forum), I am Georgian too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #33 from George Machitidze <giomac(a)gmail.com> --- @Nicolas Mailhot Thanks for details 1. If we should ditch DejaVu for legal issues - definitely, it must be done 2. Easy way - so far, only non-DejaVU font I can recommend to be GPL licensed (verified author and font) are from BPG family (https://bpgfonts.wordpress.com/2009/02/03/gpl-gnu-license-bpg-fonts/) If we need any clarification on that - I can contact him. 3. Long way - I can ask all major designers to create a font for us so we can include it somewhere, one of them already responded to my FB post regarding this issue (we have a discussion there). We can request any legal document if there is a concern - they can sign it. 4. I am not really sure about Google Noto - we don't know who is the author, but fonts are terrible and oversized (that's clearly visible) @ALAN I am Georgian, I've founded Georgian linux user group with my friends, I work on localization projects since 2004 (Ministry of Education and Science of Georgia), I am not a Fedora ambassador right now, just because I'm busy and lazy. I know what I am talking about, I'm not arguing. We've faced all these issues in 2004 and the result our work is: 0. Established relation with each-other, which was pretty hard because of different countries authors live (Georgia, Finland), differences in interests (Linux, Mac, Windows fans), difference in directions (RH fans, Canonical fans, KDE fans, GNOME fans), age gap (18 to 60 yo). We've all sat and decided to do the job the right way, usually we fight 1. Created new Georgian keyboard (MESS), included with other four keyboards in OSS XKB etc 2. BPG published fonts in GPL, while other his fonts and fonts from other people (including GEO series from Gia Shervashidze and fonts from Reno Siradze) are also available for free and virtually without limitations 3. Localization of KDE, GNOME, Fedora, Ubuntu, Windows Regarding Google Noto: Google NEVER asked anyone anything, they've even included Keyboard only few years ago, they don't know whom to ask and what to do - they've never reached us or government. Same applies to all their products and all l10n/i18n parts. We've tried, but they don't care. Same applies to Apple and both are now under heavy criticism from users as we are hardly to reading the texts and glyphs. Virtual keyboards also look ugly and are not proportional. We get no response - tried to push issues though representative officials, via government, via Georgian Mac's User Group (some of us are founding members there too) - nothing works. We were able to solve issues only with OSS software and M$. These Google fonts look REALLY BAD. It's hard to see whole picture if you haven't studied Georgian, but one thing you can easily find out - Georgian glyphs in Google Noto are HUGE. proportions are inadequate. Try to write few letters in latin Goto and then the same with Georgian, size is about 1.5 bigger. It's elementary and offensive. Who else are we looking for? If I will ask something like that to Besarioni, definitely, he'll laugh at me and never talk again (he's a man of character). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #32 from Alan <alan.g12r(a)outlook.com> --- @George Machitidze > You can read it in attached document "Mtavruli-style letters are never used as “capitals”; a word is always entirely presented in mtavruli or not" And you can also read the answer: > This statement was not correct. A number of documents from the late 19th century and early 20thcentury make use of mtavruli > characters in initial position in sentences, lines of verse, and for propernames and place-names. For example: https://ka.wikipedia.org/wiki/%E1%83%A5%E1%83%90%E1%83%A0%E1%83%97%E1%83%A3… Google Noto fonts are used as default for Georgian in Android and Arch-based distributions. They look nice. You can read here what Besarion thinks about Mtavruli (or ask him, if you have a direct communication) https://bpgfonts.wordpress.com/2016/02/24/mtavruli-for-perfection/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #31 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- @George Machitidze ### Legal aspects Much as I love the GPL and use it for my own projects it does not translate well to font files. From a legal point of view, software is derived into other software, so a license that propagates to derived works like the GPL does, works well. It’s software both parts of the equation. However, fonts can be derived into documents due to how document formats embed fonts (fully or via subsetting). Therefore, the GPL and software licenses in general are completely inadequate for font files. Most people do not want their documents GPLed just because they used a Free and Open font in them. Because the GPL is inadequate, there was quite a lot of experimenting at the start of the century to find a working license for Free and Open fonts. Some proposed font-specific GPL legal extensions. Others wrote brand new experimental licenses. In the end most everyone agreed to use the OFL, which is the font license of most Google fonts today, and the font license Fedora recommends for new font projects. DejaVu antedates all of this however. It is a direct derivative of Bitstream Vera, which was released under one of licenses people experimented with before settling on the OFL. Vera/DejaVu licensing is unlikely to change today because that would require Bitstream cooperation and probably quite a lot of money to motivate the Bistream legal department to look at it. When adding to or modifying Vera or DejaVu, you should strive to keep things simple and integrate the original Vera/DejaVu legal framework. DejaVu licensing is complex and one-of-a-kind due to the inadequacies of the original experimental Bitstream licensing. It’s not as simple as using vanilla GPL for software or the OFL for new font projects. https://github.com/dejavu-fonts/dejavu-fonts/blob/master/LICENSE When the DejaVu project was active it served as legal clearing house and made sure contributors understood and and agreed with those legal clauses. Now it is dormant, people that release DejaVu derivatives must do this work themselves. ### Font coverage aspect From a font file point of view the only thing we can do is try to integrate fonts with correct opentype metadata and correct unicode coverage. It is no use, as you wrote, to remove coverage from font files. Software that wants to use specific code-points will just fall back to fonts that include this coverage. If you want to prevent those fallbacks the only reliable way is to integrate good coverage in your font file so the fallback need not happen. If things still do not work after a font with good unicode coverage was deployed, then that means: 1. some piece or text rendering is making mistakes when applying the unicode standard. No use work-arrounding the standard by using incomplete or non-compliant font files here, you need to identify which part is misapplying the standard and get it fixed 2. the Unicode standard is wrong. Well, I sort of doubt this is the case here, but human creations are imperfect by nature. If the standard is wrong then you need to get it fixed because software implementers are applying the standard and do not have time to waste sifting through all the pseudo-standards people keep inventing all over the world. That’s the sole reason people use Unicode today. It is horribly complex, and not ideal, but having to deal with multiple conflicting encoding rules would be way worse. Chinese/Japanese/Korean people yelled for a decade Unicode made the wrong decisions for their scripts. They are using Unicode like everyone else today anyway, because the alternative to Unicode, are way worse from a software interoperability point of view. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

← Newer
1
...
4
5
6
7
8
9
10
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs May 2020