After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 565633 - pango_font_description_from_string - what are the values for style options exactly?
pango_font_description_from_string - what are the values for style options ex...
Product: pango
Classification: Platform
Component: docs
Other All
: Normal minor
: ---
Assigned To: pango-maint
Depends on:
Reported: 2008-12-25 19:15 UTC by Michael Smirnov
Modified: 2018-05-22 12:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Michael Smirnov 2008-12-25 19:15:50 UTC
Creates a new font description from a string representation in the form "[FAMILY-LIST] [STYLE-OPTIONS] [SIZE]", where FAMILY-LIST is a comma separated list of families optionally terminated by a comma, STYLE_OPTIONS is a whitespace separated list of words where each WORD describes one of style, variant, weight, stretch, or gravity, and SIZE is a decimal number (size in points) or optionally followed by the unit modifier "px" for absolute size. Any one of the options may be absent. If FAMILY-LIST is absent, then the family_name field of the resulting font description will be initialized to NULL. If STYLE-OPTIONS is missing, then all style options will be set to the default values. If SIZE is missing, the size in the resulting font description will be set to 0.

Correct version:
In addition to all above it should say what values one could use for every style option.

Other information:
Comment 1 John Boncek 2009-03-05 23:22:22 UTC
Some of this is presumably given by the various enumerations under, but that could be spelled out.
Comment 2 GNOME Infrastructure Team 2018-05-22 12:45:11 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: