Bug 522648 - glyphs cut-off below "baseline" when the font size is too big
Summary: glyphs cut-off below "baseline" when the font size is too big
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 19
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
: 661599 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2009-09-10 23:03 UTC by Jens Petersen
Modified: 2015-02-18 11:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-18 11:59:40 UTC

Attachments (Terms of Use)
firefox.png (98.01 KB, image/png)
2009-09-10 23:04 UTC, Jens Petersen
no flags Details

System ID Priority Status Summary Last Updated
GNOME Bugzilla 607419 None None None Never

Description Jens Petersen 2009-09-10 23:03:07 UTC
Description of problem:
With ipa fonts being used for Japanese desktop,
it seems the bottom of letters with parts under
the Latin "baseline" tend to get cut-off in
textboxes in Firefox.

How reproducible:
every time

Steps to Reproduce:
1. Login to rawhide Japanese gnome desktop
2. Run firefox and type "abcdefghijklmnopqrstuvwxyz" into awesome bar.
3. sudo yum install vlgothic-fonts
4. repeat (2)
Actual results:
2. Bottom of letters 'g', 'j', 'p', 'q', 'y' are clipped
4. Displays fine.

Expected results:
2. All the glyphs to be visible.

Comment 1 Jens Petersen 2009-09-10 23:04:26 UTC
Created attachment 360582 [details]

Comment 2 Jens Petersen 2009-09-11 06:02:23 UTC
So "workaround" might be just to install vlgothic-fonts
by default for Japanese desktop.

Comment 3 Akira TAGOH 2009-09-29 09:02:07 UTC
This issue has been forwarded to "upstream" and there are no way of fixing that in house (apparently fontforge is a bit buggy), I'll leave this to upstream and visit again when they have a new release in the future.

Comment 4 Akira TAGOH 2010-12-09 08:06:03 UTC
Reopened and reassigning to gtk2. see https://bugzilla.gnome.org/show_bug.cgi?id=607419

Comment 5 Akira TAGOH 2010-12-09 08:07:52 UTC
*** Bug 661599 has been marked as a duplicate of this bug. ***

Comment 6 Fedora End Of Life 2013-04-03 20:09:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 7 Fedora End Of Life 2015-01-09 21:40:28 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-02-18 11:59:40 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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