Bug 90500 - Hebrew unicode section of Nimbus Mono L is broken
Summary: Hebrew unicode section of Nimbus Mono L is broken
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: urw-fonts (Show other bugs)
(Show other bugs)
Version: 9
Hardware: All Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-08 21:32 UTC by Dov Grobgeld
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-12 21:44:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Dov Grobgeld 2003-05-08 21:32:56 UTC
Description of problem:

The font "Nimbus Mono L" included in RH9 only defines the first 16 characters of
the Hebrew alphabet (which contains 26 characters including the final forms)
starting at U+05D0. If this font is chosen for the display of Hebrew text
through fontconfig the result looks very strange, as part of the text will be
shown in part Nimbus Mono L and part in some other fallback font.

This property of the font may be verified e.g. by pfaedit or by gucharmap.

What is interesting is that the bold, the italic, and the bold-italic versions
of these fonts don't define the Hebrew unicode section at all. I think the
correct solution is to erase the Hebrew glyphs from the font alltogether, as the
 Hebrew glyphs anyhow are butt ugly.

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


How reproducible:


Steps to Reproduce:
1. run gedit
2. change the font to Nimbus mono L
3. Paste the sequence of the Hebrew alphabet into gedit:

Actual results:

    The text is shown in two different fonts

Expected results:

    One font

Additional info:

Comment 1 Owen Taylor 2003-06-12 21:44:57 UTC
Seems to be fixed in 2.1 that has a newer upstream version of the 
urw fonts.

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