Bug 2511 - Handle Ultra font weight name
Summary: Handle Ultra font weight name
Status: RESOLVED FIXED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Keith Packard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 8100
  Show dependency treegraph
 
Reported: 2005-02-09 04:55 UTC by Ross Burton
Modified: 2007-10-25 14:00 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Handle the Ultra style name (556 bytes, patch)
2005-02-09 04:56 UTC, Ross Burton
Details | Splinter Review

Description Ross Burton 2005-02-09 04:55:45 UTC
When using type 1 fonts the weights have to be invented by fontconfig from the
style names.  However, Ultra isn't handled.  The attached patch adds Ultra an
alternative for FC_WEIGHT_ULTRABOLD.
Comment 1 Ross Burton 2005-02-09 04:56:59 UTC
Created attachment 1875 [details] [review]
Handle the Ultra style name
Comment 2 Keith Packard 2005-02-24 09:54:57 UTC
The code currently looks in the style name for substrings matching the specified
names; unfortunately 'ultra' isn't unique in this regard -- a Type1 font with
'ultracondensed' in the style name will accidentally match 'ultra' as well.

Perhaps some word-boundary tests could be added which would distinguish these
two cases.
Comment 3 Keith Packard 2006-09-01 20:27:02 UTC
Please test branch 'ultra-bold' and see if this works for you. I don't have any
fonts with this characteristic. Alternatively, point me at a font which does...
Comment 4 Keith Packard 2006-09-02 19:16:05 UTC
sorry, that's the ultra-weight branch

$ git-clone git://anongit.freedesktop.org/git/fontconfig
$ cd fontconfig
$ git-checkout ultra-weight
$ sh ./autogen.sh
Comment 5 Behdad Esfahbod 2007-10-25 08:02:36 UTC
Keith, didn't you fix this?
Comment 6 Keith Packard 2007-10-25 14:00:28 UTC
yeah, fixed but never added to master. Done now.


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.