You may close this bug... This is actually a bug/feature in the font itself. The bug pertains to the Font-Family metadata, which has been set differently for both fonts.
fontconfig works as it should. So this is not a bug in fontconfig. I'm sorry for the inconvenience. -- Misidentified fonts https://launchpad.net/bugs/32008 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
