Bug 2248572 - The font "Comfortaa" does not display the number "8" correctly
Summary: The font "Comfortaa" does not display the number "8" correctly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: aajohan-comfortaa-fonts
Version: 39
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-11-07 19:23 UTC by honkhonkhonk
Modified: 2024-03-30 04:25 UTC (History)
4 users (show)

Fixed In Version: aajohan-comfortaa-fonts-3.105-0.1.20210729git2a87ac6.fc40
Clone Of:
Environment:
Last Closed: 2023-11-30 09:45:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Comparison of Fedora's and Google's Comfortaa Font (110.83 KB, image/png)
2023-11-07 19:23 UTC, honkhonkhonk
no flags Details

Description honkhonkhonk 2023-11-07 19:23:57 UTC
Created attachment 1997694 [details]
Comparison of Fedora's and Google's Comfortaa Font

Description of problem:
The font "Comfortaa" does not display the number 8 correctly,

Version-Release number of selected component (if applicable):
idk

How reproducible:
Always (for me atleast)

Steps to Reproduce:
1. Open any application or document using the "Comfortaa" font.
2. Observe the appearance of the number 8 in the text.

Actual results:
The number "8" in the Comfortaa font does not render correctly, as seen in the attached picture.

Expected results:
The font should render all characters, including the number "8," correctly.

Additional info:
This issue can be resolved by removing the existing Comfortaa font and replacing it with a version downloaded directly from Google Fonts (https://fonts.google.com/specimen/Comfortaa)

I'm using Fedora 39 (KDE Spin).

Comment 1 Luya Tshimbalanga 2023-11-08 16:33:01 UTC
Hello  honkhonkhonk,

We were able to reprodue that issue. The packaged Comfortaa is identical to Google Fonts version, only difference is possible an parsing error in the packaged version. We will take a look at the root cause.

Comment 2 honkhonkhonk 2023-11-10 14:42:48 UTC
I have observed that the font rendering issue can be reproduced when creating a virtual machine using the Fedora KDE ISO.

Comment 3 Akira TAGOH 2023-11-15 07:52:00 UTC
This is because a font at Google Fonts is newer than the font we shipped.

$ otfinfo -v /usr/share/fonts/aajohan-comfortaa-fonts/Comfortaa-Regular.otf
Version 3.101;PS 003.101;hotconv 1.0.88;makeotf.lib2.5.64775

$ otfinfo -v ~/Downloads/Comfortaa/static/Comfortaa-Regular.ttf
Version 3.105

That may contains unreleased changes since 2017:
https://github.com/googlefonts/comfortaa/compare/3.101...main

Comment 4 Luya Tshimbalanga 2023-11-26 11:09:45 UTC
Can you test https://download.copr.fedorainfracloud.org/results/@designsuite/fonts/fedora-39-x86_64/06695457-aajohan-comfortaa-fonts/ please to see if the issue get resolved? If so, we will make it available on the main repository.

Comment 5 Akira TAGOH 2023-11-30 07:37:38 UTC
That looks good to me.

$ rpm -q aajohan-comfortaa-fonts
aajohan-comfortaa-fonts-3.105-1.20210729git2a87ac6.fc39.noarch
$ hb-view --font-file /usr/share/fonts/aajohan-comfortaa-fonts/Comfortaa-Regular.otf --text 8
       ▂▄▆▇▇▇▆▄▂       
      ▟ ▁▄▆▆▆▄▁ ▙      
     ▌ ▉       ▏ ▌     
     ▍ ▊       ▎ ▋     
     ▙▖ ▙▂   ▂▟ ▗      
       ▖   ▇   ▊       
     ▃▇ ▂▄▅▆▅▄▂ ▇▃     
    ▌  ▟       ▙  ▌    
    ▏ ▌         ▍ ▉    
    ▏ ▋         ▍ ▉    
    ▙  ▄       ▄  ▟    
     ▙▂ ▇▅▄▄▄▅  ▂▟     
       ▇▅▄▃▃▃▄▅▇

Comment 6 Fedora Update System 2023-11-30 09:42:17 UTC
FEDORA-2023-f7e498ee98 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f7e498ee98

Comment 7 Fedora Update System 2023-11-30 09:45:48 UTC
FEDORA-2023-f7e498ee98 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Red Hat Bugzilla 2024-03-30 04:25:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.