On 09/12/2012 11:06 AM, Raimund Steger wrote: > Werner LEMBERG wrote: > > As I see it that would require major changes in the matcher because family > name substitution is normally only possible through rules. > I'm rather certain it's not worth the effort (and additional user confusion), > I can't imagine a use case for it and if there is one, I'd say it's better > done with rules. (The tide might turn here someday though if some kind of > native family grouping should be implemented.) I'm of the exact same opinion. > Even in that spec the following paragraph suggests that there should still be > a way to select fonts by their unfiltered names. Let's just call the > additional values in the 'family' property fontconfig's implementation of that > suggestion. > > Raimund > > _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig