OS X fails to support comma-separated font list
Submitted by Peter Bowen
Assigned to Kristian Rietveld @kristian
Link to original bug (#762873)
Description
On OS X, if one passes a string containing a comma-separated font list to pango_font_description_set_family, the result is no font matches. Passing the members one at a time shows that each individual name is recognized and used properly.
For example:
pango-view --no-display --output out1.png --text '0123456789 - @ The lazy fox something something' --font "Anonymous Pro Minus, monospace" renders an image using a proportional sans-serif font (not monospace). pango-view --no-display --output out2.png --text '0123456789 - @ The lazy fox something something' --font "Anonymous Pro Minus" renders using Anonymous. pango-view --no-display --output out3.png --text '0123456789 - @ The lazy fox something something' --font "monospace" renders using a monospace font that is not Anonymous. pango-view --no-display --output out4.png --text '0123456789 - @ The lazy fox something something' --font "QuuxXyzzy" renders identically to the first one. QuuxXyzzy is a made up string that does not match any font on my system.
Version: 1.38.x