Bug 9089 - usFirstCharIndex value in OS2 table incorrect
Summary: usFirstCharIndex value in OS2 table incorrect
Status: RESOLVED NOTOURBUG
Alias: None
Product: DejaVu
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Deja Vu bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-19 23:27 UTC by Roozbeh Pournader
Modified: 2006-11-20 14:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Roozbeh Pournader 2006-11-19 23:27:24 UTC
According to a part of the OpenType standard at the following address:

http://www.microsoft.com/typography/otspec/os2.htm#fci

The usFirstCharIndex value should contain "The minimum Unicode index (character
code) in this font, according to the cmap subtable for platform ID 3 and
platform- specific encoding ID 0 or 1."

This is not counting the value 0, which is the ".notdef" character. This means
that the value should be 0x20 for all the DejaVu fonts, as space is the first
character supported. But the value in the fonts, according to TTX and also MS
font validator is 0x0d (13 decimal).
Comment 1 Ben Laenen 2006-11-20 04:06:34 UTC
I think FontForge is automatically putting that value there, because I can't 
find a place to set that value. Going to forward this to the FontForge mailing 
list.
Comment 2 Ben Laenen 2006-11-20 14:44:44 UTC
George Williams has patched this in FontForge, should work now with latest svn 
of FF.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.