fonts-bugs August 2021

fonts-bugs@lists.fedoraproject.org

1 participants
51 discussions

[Bug 1999078] New: Hinting broken for Bitstream Vera/DejaVu in Epiphany
by bugzilla＠redhat.com 27 Nov '24

27 Nov '24

https://bugzilla.redhat.com/show_bug.cgi?id=1999078 Bug ID: 1999078 Summary: Hinting broken for Bitstream Vera/DejaVu in Epiphany Product: Fedora Version: 34 Status: NEW Component: freetype Assignee: mkasik(a)redhat.com Reporter: ossman(a)cendio.se QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, kevin(a)tigcc.ticalc.org, mark(a)net-c.com, mclasen(a)redhat.com, mkasik(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1819062 --> https://bugzilla.redhat.com/attachment.cgi?id=1819062&action=edit Screenshot with varying sub pixel placement Description of problem: After upgrading from Fedora 33 to Fedora 34, there is some extremely odd hinting bug in Epiphany. The same glyph appears with different amount of hinting in the same line of text, causing a very odd and blurry appearance. Version-Release number of selected component (if applicable): freetype-2.10.4-3.fc34.x86_64 bitstream-vera-sans-fonts-1.10-41.fc33.noarch dejavu-sans-fonts-2.37-16.fc34.noarch epiphany-40.3-1.fc34.x86_64 webkit2gtk3-2.32.3-1.fc34.x86_64 pango-1.48.9-2.fc34.x86_64 How reproducible: 100% Steps to Reproduce: 1. Configure Epiphany to use Bitstream Vera or DejaVu Sans Book 2. Configure full hinting Actual results: Fully hinted, consistent glyphs. Expected results: Some glyphs are fully hinted, some look like they've been offset by a fraction of a pixel. (See screenshot) Additional info: So far I'm only seeing this in Epiphany. I still filed this for freetype since as far as I know it is freetype that does all glyph layout, hinting and sub-pixel stuff. Feel free to move as appropriate. So it seems odd that a bug in Epiphany can screw this up. -- You are receiving this mail because: You are on the CC list for the bug.

1 43

[Bug 1833858] New: Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 27 Nov '24

27 Nov '24

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Bug ID: 1833858 Summary: Hangul Jamo is seperated and printed respectively Product: Fedora Version: 32 Status: NEW Component: google-droid-fonts Assignee: nicolas.mailhot(a)laposte.net Reporter: hyunwoo.park(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, oliver(a)redhat.com, paul(a)frixxon.co.uk, tremble(a)tremble.org.uk Target Milestone: --- Classification: Fedora Created attachment 1687129 --> https://bugzilla.redhat.com/attachment.cgi?id=1687129&action=edit wrong display of Hangul at LibreOffice Writer Description of problem: When Hangul is output to the monitor, Chosung, Neutral, and Jongseong are output separately. Version-Release number of selected component (if applicable): Font file, /usr/share/fonts/google-droid-sans-fonts/DroidSansFallbackFull.ttf, of google-droid-sans-fonts-20200215-3.fc32.noarch How reproducible: If you create a test.html containing "가속도" and open the file in the chrome browser, the Korean alphabet will be displayed separately. Or, write "가속도" at LibreOffice Writer and select font as "Droid Sans Fallback". Steps to Reproduce: 1. write "가속도" at LibreOffece Writer 2. select the text and change font name to "Droid Sans Fallback" Actual results: The text is displayed like "가ㅅㅗㄱㄷㅗ". Expected results: Text should be "가속도" Additional info: https://kldp.org/node/163247 -- You are receiving this mail because: You are on the CC list for the bug.

1 43

[Bug 1999864] New: Cannot find package with font for Coptic although such a package exists for Fedora 34
by bugzilla＠redhat.com 19 Sep '24

19 Sep '24

https://bugzilla.redhat.com/show_bug.cgi?id=1999864 Bug ID: 1999864 Summary: Cannot find package with font for Coptic although such a package exists for Fedora 34 Product: Fedora Version: 34 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pnemade(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1819530 --> https://bugzilla.redhat.com/attachment.cgi?id=1819530&action=edit Gnome Software unable to find Coptic fonts Using Fedora-Workstation-Live-x86_64-34-1.2.iso in qemu. I played with emoji picker and Gnome popped up something requesting more fonts. I clicked and then Gnome Software said: “Unable to find the Coptic, Persian, Old (ca. 600-400 B.C.), Ugaritic you were searching for. Please see _the documentation_ for more information.” See attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1761885] New: rpm -V complains about mode for ghost .uuid files
by bugzilla＠redhat.com 25 Feb '24

25 Feb '24

https://bugzilla.redhat.com/show_bug.cgi?id=1761885 Bug ID: 1761885 Summary: rpm -V complains about mode for ghost .uuid files Product: Fedora Version: rawhide Status: NEW Component: fontpackages Assignee: nicolas.mailhot(a)laposte.net Reporter: mtasaka(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk, redhat-bugzilla(a)linuxnetz.de, tagoh(a)redhat.com Target Milestone: --- Link ID: Red Hat Bugzilla 1564432 Classification: Fedora Description of problem: rpm -Va complains a lot about mode of %ghost .uuid files: .M....... g /usr/share/fonts/paktype-naqsh/.uuid .M....... g /usr/share/fonts/lilypond/.uuid .M....... g /usr/share/fonts/sil-padauk/.uuid .M....... g /usr/share/fonts/google-droid/.uuid .M....... g /usr/share/fonts/lilypond/.uuid .M....... g /usr/share/fonts/smc-suruma/.uuid .M....... g /usr/share/fonts/google-android-emoji/.uuid .M....... g /usr/share/fonts/google-crosextra-carlito/.uuid .M....... g /usr/share/fonts/lohit-assamese/.uuid .M....... g /usr/share/fonts/dejavu/.uuid .M....... g /usr/share/fonts/lohit-telugu/.uuid .M....... g /usr/share/fonts/lilypond/.uuid ..... Looks like fontpackages-devel template rpmmacro creates .uuid which %ghost %atttr(0000) e.g. [root@localhost ~]# rpm -qf /usr/share/fonts/google-droid/.uuid google-droid-sans-fonts-20120715-16.fc31.noarch [root@localhost ~]# rpm -qlv google-droid-sans-fonts | grep uuid ---------- 1 root root 0 7月 25 23:03 /usr/share/fonts/google-droid/.uuid ref: https://src.fedoraproject.org/rpms/fontpackages/blob/master/f/fontpackages-… but I guess %transfiletriggerin script by fontconfig creates .uuid as 0755 permission (perhaps) Version-Release number of selected component (if applicable): fontpackages-filesystem-1.44-25.fc31.noarch fontconfig-2.13.92-3.fc31.x86_64 fontconfig-2.13.92-3.fc31.i686 google-droid-sans-fonts-20120715-16.fc31.noarch How reproducible: 100% Steps to Reproduce: 1. See above, try $ rpm -Va 2. 3. Actual results: See above, lots of .uuid permission complaint Expected results: No complaint by rpm -Va Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1727602] New: Fedora flatpak for this app on registry.fedoraproject.org
by bugzilla＠redhat.com 30 Jun '23

30 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1727602 Bug ID: 1727602 Summary: Fedora flatpak for this app on registry.fedoraproject.org Product: Fedora Version: rawhide Status: NEW Component: fontforge Assignee: kevin(a)scrye.com Reporter: 7d28c752(a)opayq.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, kevin(a)scrye.com, paul(a)frixxon.co.uk, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora It would be great if you could provide a flatpak package of this app to https://registry.fedoraproject.org/. Especially for users of Fedora Silverblue https://silverblue.fedoraproject.org/ this then allows a seamless installation and upgrades without rebooting the system (just restarting the application). Additionally, flatpaks can of course be installed on any distro, so also non-Fedora users could use it too. More details: * https://fedoraproject.org/wiki/Workstation/Flatpaks * https://fedoraproject.org/wiki/Changes/Graphical_Applications_as_Flatpaks I know this app is available on Flathub as a flatpak, but I still prefer Fedora's package testing/QA etc., that's why I'd also like to have a version on https://registry.fedoraproject.org/. Also Flathub is a third-party source from the Fedora users/projects viewpoint, so I guess some users would not like to use third-party app sources. However, the fact that it is on Flathub should make it easier for you to implement this, because you can have a look on how they do it. (Not that you need to do everything in the same way, but it proves it is possible to package as a flatpak, at least.) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla＠redhat.com 03 Jun '23

03 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1813728 Bug ID: 1813728 Summary: Square four dot Unicode character has incorrect glyph Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: pango Severity: low Assignee: pwu(a)redhat.com Reporter: guillaumepoiriermorency(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mclasen(a)redhat.com, pwu(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: The glyph for the Unicode "square four dot" character is incorrect. Version-Release number of selected component (if applicable): I think this problem arose when upgrading from Fedora 30 to Fedora 31. How reproducible: The simplest way is to start GNOME Characters Map and search for "square four dot". -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1898319] New: dejavu-lgc-sans-mono-fonts: Misleading summary
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=1898319 Bug ID: 1898319 Summary: dejavu-lgc-sans-mono-fonts: Misleading summary Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: dejavu-fonts Severity: low Assignee: nicolas.mailhot(a)laposte.net Reporter: van.de.bugger(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk, peter(a)thecodergeek.com Target Milestone: --- Classification: Fedora Description of problem: Summary of dejavu-lgc-sans-mono-fonts is misleading. It is: "A variable-width Latin-Greek-Cyrillic mono-space font family". Accordingly to Wikipedia: > A monospaced font, also called a fixed-pitch, fixed-width, or non-proportional font, is a font whose letters and characters each occupy the same amount of horizontal space. This contrasts with variable-width fonts, where the letters and spacings have different widths. So, a font is either monospaced or variable-width but not both, these are mutually exclusive concepts. How dejavu-lgc-sans-mono-fonts can be "a variable-width mono-space font family"?? Version-Release number of selected component (if applicable): dejavu-lgc-sans-mono-fonts-2.37-15.fc33 How reproducible: Always. Steps to Reproduce: 1. $ dnf info dejavu-lgc-sans-mono-fonts Actual results: Summary : A variable-width Latin-Greek-Cyrillic mono-space font family Expected results: Summary : A Latin-Greek-Cyrillic mono-space font family -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla＠redhat.com 26 Apr '23

26 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1779123 Bug ID: 1779123 Summary: Pango no longer supports type1 fonts Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: mjg(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mclasen(a)redhat.com, pwu(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: In pango 1.44, pango dropped support for type1 fonts. Therefore, no application which uses pango for font loading can use type1 fonts any more. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 (and later) How reproducible: always Steps to Reproduce: 1. Upgrade F31 or rawhide 2. Open any pango-using application 3. Try to use type1 font Actual results: No type1 font is usable Expected results: Type1 font is usable Additional info: bug 1753295 is the same bug for dropped bitmap font support. Over there, workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are discussed. An attempt to discuss type1 there failed. This bug here is specifically about type1 fonts to discuss ways (or their absence) to deal with pangos dropped type 1 support. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1857488] New: fontawesome-fonts-5.14.0 is available
by bugzilla＠redhat.com 07 Apr '23

07 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1857488 Bug ID: 1857488 Summary: fontawesome-fonts-5.14.0 is available Product: Fedora Version: rawhide Status: NEW Component: fontawesome-fonts Keywords: FutureFeature, Triaged Assignee: pvoborni(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, mrunge(a)redhat.com, pvoborni(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 5.14.0 Current version/release in rawhide: 4.7.0-8.fc32 URL: http://fontawesome.io Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/826/ -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1895482] New: Liberation Fonts Support For Serbian locl Glyphs Incomplete
by bugzilla＠redhat.com 04 Apr '23

04 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1895482 Bug ID: 1895482 Summary: Liberation Fonts Support For Serbian locl Glyphs Incomplete Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: liberation-fonts Assignee: vishalvijayraghavan(a)gmail.com Reporter: aleslavista(a)outlook.it QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, petersen(a)redhat.com, psatpute(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1727218 --> https://bugzilla.redhat.com/attachment.cgi?id=1727218&action=edit Correctly Localized Glyphs Description of problem: Liberation Fonts do NOT provide full support for Serbian localized glyphs. Version-Release number of selected component (if applicable): Liberation-Fonts 2.1-1-1 How reproducible: You need a program that is able to access the font's localized glyphs: usually that's LibreOffice Writer. Steps to Reproduce: 1. Open LibreOffice Writer 2. Type бгдпт, then бгдпт in Italic, бгдпт in Bold and finally бгдпт in Italic Bold with Liberation Serif, and do the same with Liberation Sans 3. Set the language to "Serbian Cyrillic" Actual results: Not all glyphs are correctly localized Expected results: See attachment for correctly localized glyphs Additional info: Liberation Mono has slanted Italic, therefore only the first glyph should be localized: CYRILLIC LETTER SMALL BE. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs August 2021