June 2022 - fonts-bugs - Fedora Mailing-Lists

[Bug 2059771] New: Please branch and build google-roboto-fonts in epel9

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2059771 Bug ID: 2059771 Summary: Please branch and build google-roboto-fonts in epel9 Product: Fedora EPEL Version: epel9 Status: NEW Component: google-roboto-fonts Assignee: dtardon(a)redhat.com Reporter: dcavalca(a)fb.com QA Contact: extras-qa(a)fedoraproject.org CC: dtardon(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Please branch and build google-roboto-fonts in epel9. If you do not wish to maintain google-roboto-fonts in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/google-roboto-fonts/addgroup and grant it commit access, or collaborator access on epel* branches. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059771

1 year, 9 months

1
6
0 / 0

[Bug 1837850] New: Unable to open Noto CJK fonts properly because of no cidmap file

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1837850 Bug ID: 1837850 Summary: Unable to open Noto CJK fonts properly because of no cidmap file Product: Fedora Version: rawhide Status: NEW Component: fontforge Assignee: kevin(a)scrye.com Reporter: tagoh(a)redhat.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 Description of problem: When going to open Noto CJK fonts on fontforge, fontforge opens an error dialog that claims no cidmap file found. Version-Release number of selected component (if applicable): fontforge-20200314-5.fc32.x86_64 How reproducible: always Steps to Reproduce: 1.fontforge /usr/share/fonts/google-noto-cjk/NotoSansCJK-Regular.ttc 2.Select any family names in the list 3. Actual results: Open an error dialog claims: FontForge was unable to find a cidmap file for this font. It is not essential to have one, but some things will work better if you do. if you have not done so you might want to download the cidmaps from: http://FontForge.sourceforge.net/cidmaps.tgz and then gunzip and untar them and move them to: /usr/share/fontforge Expected results: should start loading a font Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 year, 10 months

1
11
0 / 0

[Bug 2067200] New: fonttools fails to build with Python 3.11: AssertionError: assert 'UFOFormatVersion.FORMAT_3_0' == '3.0'

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2067200 Bug ID: 2067200 Summary: fonttools fails to build with Python 3.11: AssertionError: assert 'UFOFormatVersion.FORMAT_3_0' == '3.0' Product: Fedora Version: rawhide Status: NEW Component: fonttools Assignee: pnemade(a)redhat.com Reporter: thrnciar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, mhroncok(a)redhat.com, pnemade(a)redhat.com, sshedmak(a)redhat.com, tagoh(a)redhat.com, thrnciar(a)redhat.com Blocks: 2016048 (PYTHON3.11) Target Milestone: --- Classification: Fedora fonttools fails to build with Python 3.11.0a6. =================================== FAILURES =================================== ___________________________ test_formatVersionTuple ____________________________ ufo_path = PosixPath('/tmp/pytest-of-mockbuild/pytest-0/test_formatVersionTuple0/TestFont.ufo') def test_formatVersionTuple(ufo_path): reader = UFOReader(ufo_path) assert reader.formatVersionTuple == (3, 0) assert reader.formatVersionTuple.major == 3 assert reader.formatVersionTuple.minor == 0 > assert str(reader.formatVersionTuple) == "3.0" E AssertionError: assert 'UFOFormatVersion.FORMAT_3_0' == '3.0' E - 3.0 E + UFOFormatVersion.FORMAT_3_0 https://docs.python.org/3.11/whatsnew/3.11.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora... For all our attempts to build fonttools with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/fontt... Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.11: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ Let us know here if you have any questions. Python 3.11 is planned to be included in Fedora 37. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.11. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2016048 [Bug 2016048] Python 3.11 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2067200

1 year, 10 months

1
4
0 / 0

New: Quotation Request

by Anwar＠fedoraproject.org

1 year, 10 months

1
0
0 / 0

[Bug 2098473] New: Roboto Mono font not selectable in GNOME Terminal, needs update

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2098473 Bug ID: 2098473 Summary: Roboto Mono font not selectable in GNOME Terminal, needs update Product: Fedora Version: 36 Hardware: All OS: Linux Status: NEW Component: google-roboto-mono-fonts Severity: low Assignee: link(a)sub-pop.net Reporter: plroskin(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, link(a)sub-pop.net Target Milestone: --- Classification: Fedora Description of problem: Fedora ships an old version of Google Roboto Mono fonts. There are not marked as monospaced. As a result, Roboto Mono cannot be selected in GNOME Terminal. In contrast, manually downloaded Roboto Mono fonts are selectable in GNOME Terminal. On top of that, it's recommended to use variable (weight) fonts. Fedora ships fonts with fixed weight. Version-Release number of selected component (if applicable): google-roboto-mono-fonts-2.002-0.5.20200129git.fc36.noarch How reproducible: Always (make sure to close and open GNOME Terminal when fonts are installed/uninstalled) Steps to Reproduce: 1. Install google-roboto-mono-fonts 2. Reboot 3. Log in 4. Open GNOME Terminal 5. ≡ -> Preferences -> Unnamed -> Text -> Custom Font Actual results: Roboto Mono is not in the list Expected results: Roboto Mono is in the list Additional info: The latest files can be found in https://github.com/googlefonts/RobotoMono Note that there are fonts/ttf and fonts/variable Exactly the same files (variable fonts only) can be found in the Google fonts snapshot at https://github.com/google/fonts/archive/main.zip -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2098473

1 year, 10 months

1
3
0 / 0

[Bug 2044960] New: F36FailsToInstall: python3-fonttools+unicode

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2044960 Bug ID: 2044960 Summary: F36FailsToInstall: python3-fonttools+unicode Product: Fedora Version: rawhide Status: NEW Component: fonttools Assignee: pnemade(a)redhat.com Reporter: mhroncok(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com, sshedmak(a)redhat.com, tagoh(a)redhat.com Blocks: 1992487 (F36FailsToInstall,RAWHIDEFailsToInstall) Target Milestone: --- Classification: Fedora Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok(a)redhat.com). Your package (fonttools) Fails To Install in Fedora 36: can't install python3-fonttools+unicode: - nothing provides python3.10dist(unicodedata2) >= 14 needed by python3-fonttools+unicode-4.29.0-1.fc36.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter... Thanks! Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1992487 [Bug 1992487] Fedora 36 Fails To install Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2044960

1 year, 10 months

1
6
0 / 0

[Bug 2062386] New: strange font priorities in Firefox

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2062386 Bug ID: 2062386 Summary: strange font priorities in Firefox Product: Fedora Version: 35 Hardware: x86_64 OS: Linux Status: NEW Component: Fonts Assignee: i18n-bugs(a)lists.fedoraproject.org Reporter: skyfaller(a)gmail.com QA Contact: fonts-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: Sometimes, when using a native font stack in CSS on a web page, fonts that are not in the font stack at all are substituted for the desired fonts. This only seems to affect web pages viewed using: - Fedora (not Ubuntu, Debian 11, or Manjaro) - Firefox (not Chrome or Chromium) - When using the RPM version or Mozilla's official build from their website (not the Flatpak) Happens in the stable version of Firefox, Firefox Beta, and Firefox nightly. Two substitutions I've identified so far: - Droid Sans is substituted for Open Sans - P052 is substituted for 'URW Palladio L' or Palatino Substituting for Palatino may be less objectionable, since that's a generic choice, but URW Palladio L is rather specific and it's surprising to see the substitution. This also wouldn't be as objectionable if the font substitutions were better. Droid Sans doesn't look much like Open Sans at all, and P052 looks really ugly (it has unevenly sized letters). In Firefox Flatpak, it instead substitutes the better-looking 'TeX Gyre Pagella', and only does that for Palatino, not for 'URW Palladio L' (which was higher priority in my font stack). This is more desirable behavior. The source of the problem seems to be that if you run the following command: fc-match :family="Open Sans" It returns Droid Sans. Possibly related bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1820166 https://bugzilla.mozilla.org/show_bug.cgi?id=1406790 How reproducible: Consistently Steps to Reproduce: 1. Open a clean Fedora 35 install, and verify that Open Sans is not installed. 2. Create the following web page and view it in a browser: ``` <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title></title> <style> h1,h2,h3,h4 { font-family: Open Sans, Fira Sans; } </style> </head> <body> <h1>Hello World</h1> <p>Lorem ipsum dolor sit amet.</p> </body> </html> ``` Alternately, view a real live (but more complex) website at https://www.maximumethics.dev/ Actual results: Notice that the text on the webpage is displayed in Droid Sans, not Open Sans. Expected results: The webpage displays the next available font in the font stack, Fira Sans in this case, or the browser's default font if you don't have Fira Sans. -- You are receiving this mail because: You are the QA Contact for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2062386

1 year, 10 months

1
4
0 / 0

[Bug 517789] Droid Sans overrides default Japanese desktop font

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=517789 Red Hat One Jira (issues.redhat.com) <redhat-one-jira(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Link ID| |Red Hat Issue Tracker | |FC-472 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=517789

1 year, 10 months

1
0
0 / 0

[Bug 517789] Droid Sans overrides default Japanese desktop font

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=517789 Jens Petersen <petersen(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|low |high Severity|medium |high -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=517789

1 year, 10 months

1
0
0 / 0

[Bug 517789] Droid Sans overrides default Japanese desktop font

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=517789 Jens Petersen <petersen(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |i18n -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=517789

1 year, 10 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 June 2022