[Bug 1833858] New: Hangul Jamo is seperated and printed respectively
by bugzilla@redhat.com
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 week, 4 days
[Bug 1999078] New: Hinting broken for Bitstream Vera/DejaVu in
Epiphany
by bugzilla@redhat.com
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 week, 6 days
[Bug 2088665] New: Noto Sans is chosen to display symbol characters
it doesn't contain
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2088665
Bug ID: 2088665
Summary: Noto Sans is chosen to display symbol characters it
doesn't contain
Product: Fedora
Version: 36
Status: NEW
Component: google-noto-fonts
Assignee: tagoh(a)redhat.com
Reporter: talk(a)danielflaum.net
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1881507
--> https://bugzilla.redhat.com/attachment.cgi?id=1881507&action=edit
A zipped sample PDF and image of relevant portion of PDF when affected by the
issue
Description of problem:
Given a PDF lacking embedded fonts which use certain characters (including →
and ≥), GNOME's Evince on Fedora 36 chooses to substitute the Noto Sans font,
which does not include these characters.
Version-Release number of selected component (if applicable):
How reproducible:
Successfully reproduced by two people independently.
Steps to Reproduce:
1. Boot a fresh copy of Fedora 36 (the Live version in a VM will do).
2. Open the attached sample PDF in GNOME Evince (aka Document Viewer).
3. Observe the missing characters in the second paragraph from the top of the
page.
Actual results:
See attached image.
Expected results:
The missing characters should be displayed properly as → (that is,
https://unicode-table.com/en/2192/).
Additional info:
The filer initially sought help at
https://ask.fedoraproject.org/t/missing-characters-in-pdfs-since-upgrade-...,
which may be informative in reproducing the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2088665
2 weeks
[Bug 2087984] New: Version of Source Code Pro currently packaged
breaks in some cases
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2087984
Bug ID: 2087984
Summary: Version of Source Code Pro currently packaged breaks
in some cases
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: adobe-source-code-pro-fonts
Severity: medium
Assignee: mattrose(a)folkwolf.net
Reporter: jharmiso(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org, mark(a)net-c.com,
mattrose(a)folkwolf.net
Target Milestone: ---
Classification: Fedora
Created attachment 1880946
--> https://bugzilla.redhat.com/attachment.cgi?id=1880946&action=edit
A screenshot of dmesg in Alacritty with Source Code Pro selected
Description of problem:
Source Code Pro version 2.030, currently packaged for all versions of Fedora
and in EPEL, includes an SVG table that causes the freetype library to be
unable to calculate cell height, resulting in unusable output with lines
stacked on top of each other.
Version-Release number of selected component (if applicable):
2.030.1.050-<any>
How reproducible:
Always
Steps to Reproduce:
1. Install adobe-source-code-pro-fonts and alacritty (a terminal emulator that
uses freetype through the crossfont crate) from the current release versions.
2. Configure alacritty to use Source Code Pro. Example config:
~/.config/alacritty/alacritty.yml:
```yaml
font:
normal:
family: Source Code Pro
style: Regular
bold:
family: Source Code Pro
style: Bold
italic:
family: Source Code Pro
style: Italic
bolt_italic:
family: Source Code Pro
style: Bold Italic
size: 10
```
3. Launch alacritty and attempt to use the terminal
Actual results:
The terminal is completely unusable with 1px line height, although the font is
rendering at the correct size.
Expected results:
The terminal has a normal font display behavior and is usable.
Additional info:
2.038 is available and appears to fix the issue
(https://github.com/adobe-fonts/source-code-pro/releases)
See some additional discussion here:
https://github.com/alacritty/alacritty/issues/6048
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2087984
3 months
[Bug 2063714] New: serif:lang=ja falls back to Droid Sans instead of
Noto Sans CJK JP
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2063714
Bug ID: 2063714
Summary: serif:lang=ja falls back to Droid Sans instead of Noto
Sans CJK JP
Product: Fedora
Version: 36
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: petersen(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
Description of problem:
In Fedora 36 when google-noto-serif-cjk-ttc-fonts is not installed
fontconfig seems to fall back to google-droid-sans-fonts
rather than google-noto-sans-cjk-ttc-fonts.
This might be related to/caused by bug 517789?
How reproducible:
100%
Steps to Reproduce:
1. boot Fedora Live image
2. fc-match serif:lang=ja
Actual results:
2. DroidSansJapanese.ttf: "Droid Sans" "Regular"
Expected results:
2. NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular"
Additional info:
I get the same result with your older copr repo applied F35 fwiw.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2063714
3 months, 3 weeks
[Bug 1727602] New: Fedora flatpak for this app on
registry.fedoraproject.org
by bugzilla@redhat.com
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.
5 months
[Bug 1813728] New: Square four dot Unicode character has incorrect
glyph
by bugzilla@redhat.com
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.
6 months
[Bug 1898319] New: dejavu-lgc-sans-mono-fonts: Misleading summary
by bugzilla@redhat.com
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.
6 months, 1 week
[Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla@redhat.com
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.
7 months, 1 week