GNOME Bugzilla – Bug 341213
font dialogue does not show styles, which is confusing
Last modified: 2018-05-22 12:17:32 UTC
Please describe the problem: If a font comes with several style variations, all the variations are lumped together, so the font menu for me has five entries for Adobe Caslon, then five more for Adobe Caslon Bold, and so on. If I do fc-list | grep "Adobe Caslon" | sort, I see this: Adobe Caslon:style=Bold Adobe Caslon:style=Bold Alternate Adobe Caslon:style=Bold Expert Adobe Caslon:style=Bold Italic Adobe Caslon:style=Bold Italic Alternate Adobe Caslon:style=Bold Italic Expert Adobe Caslon:style=Bold Oldstyle Figures Adobe Caslon:style=Italic Adobe Caslon:style=Italic Alternate Adobe Caslon:style=Italic Expert Adobe Caslon:style=ItalicOsF Adobe Caslon:style=Ornaments Adobe Caslon:style=Regular Adobe Caslon:style=Regular Alternate Adobe Caslon:style=Regular Expert Adobe Caslon:style=Regular Small Caps & Oldstyle Figures Adobe Caslon:style=Semibold Adobe Caslon:style=Semibold Alternate Adobe Caslon:style=Semibold Expert Adobe Caslon:style=Semibold Italic Adobe Caslon:style=Semibold Italic Alternate Adobe Caslon:style=Semibold Italic Expert Adobe Caslon:style=SemiboldSC Adobe Caslon:style=Swash Bold Italic Adobe Caslon:style=Swash Italic Adobe Caslon:style=Swash Semibold Italic The Expert Set fonts have a different encoding than the regular ones, and contain special characters (e.g. ffl ligature). When I choose any of the "Adobe Caslon" entries from the font menu in the Text tool options box, GIMP remembers which I chose (e.g. so next time I click on the Aa icon the third Adobe Caslon might be highlighted) but they all display the same as each other. A possible answer might be, move to opentype, but GIMP doesn't give me access to opentype features yet; the older Expert Set fonts are a way to do this, except GIMP seems to have problems. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 65138 [details] screenshot of fonts menu Here is a screenshot of the fonts menu with duplicate Adobe Caslon entries.
Should probably be marked as a duplicate of bug #168102.
Liam, what versions of fontconfig and Pango are you using? This could very well be a fontconfig/pango problem that might even have been fixed already. Could be a simmilar problem as described in bug #303494.
Some more details: OS: Mandriva cooker fontconfig-2.3.95-1mdk pango-1.12.2-3mdk gimp-2.3.8-1mdk Inkscape also has a similar problem, which others have also reported seeing, https://sourceforge.net/tracker/?func=detail&atid=604306&aid=904962&group_id=93438 I get the same thing happening with e.g. Dante and Van Dijk, both of which have Expert variants. Poliphilus (which has only a Roman and a Roman Expert) does show two entries, although it's not clear to me how to type characters in this encoding: everything comes out in Sans instead. For Caslon, though, there are non-Expert variants that I'd like to use. So maybe there are some bigger issues here, but I think they are separate from the bug (whether in GIMP or in Pango) that the font list entries are indistinguishable.
Please report this against Pango or reassign this bug-report. I don't see any way how this could be fixed in GIMP. We are just using the result of pango_font_description_to_string().
Created attachment 88642 [details] Test program exposing the problem This is a small demo application exposing the problem that pango does not create unique strings for pango_font_description_to_string(). The fonts used in this example are generated from the SFD descriptions avilable on http://www.levien.com/type/myfonts/ - I'll attach the two fonts in a few minutes. The example code checks for the family being "LeBe" to not spew lots of stuff on the terminal. The strings should be unique for each font description returned by pango_font_family_list_faces().
Created attachment 88643 [details] First LeBe font file
Created attachment 88644 [details] Second LeBe Font file
-- 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: https://gitlab.gnome.org/GNOME/pango/issues/45.