Ah well - you're right that font handling is odd in this case. However,
my feeling is that it makes no sense to have this as an Ubuntu bug
without the font files attached and without anyone caring. And nobody
cares: Canonical has closed the bug ("proprietary font") and I (as first
submitter to Canonical) have found a solution (I edited the font's
"preferred family" field).So if fontconfig hackers are interested from a font-nerd's view - I'll gladly send the fonts that made things go wrong. However, if this is just a bug that will sit here, without a proper font to test it and without anyone caring about how fontconfig handles it - then the bug should be closed. It's orphaned, it's only parent (that's me) walked away. I don't want to be bugged by the closing of another 2 year old bug in february 2011, "because there has been no activity for this bug for 730 days". -- EurekaSans font family shows as multiple individual fonts. Expecting one font family (worked in Dapper) https://bugs.launchpad.net/bugs/330517 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
