Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
--- Comment #11 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2011-05-24
05:10:09 EDT ---
(In reply to comment #10)
(In reply to comment #9)
> Generally speaking, changing the fonts so their metadata is fontconfig-friendly
> is usually the best choice.
I ought to be able to do that by taking apart the existing TTF files and
rebuilding them, right?
Yes (if you can do it legally). Change the font in fontforge, or script the
modification with ttx, whatever works best for you
All I need to do is work out what you mean by
In what way is the current metadata, as shown in the attachment in comment 5,
I don't claim to know fontconfig/pango innards, but at a guess fontconfig is
confused by the way the fonts declare styles twice, both the legacy way
(regular, bold, italic, with medium in the family name) and the modern way
(with medium in the style name)
Medium is a weight attribute and should only appear in the style name to be
WWS-compliant. Regular is a *different* width attribute so Regular Medium is a
train wreck (see
ignore all the parts except the naming section, the fontconfig syntax at the
end is especially unreliable but the naming section is solid)
If you want the full story read
Remembering that fontconfig does *not* implement the naming fixing heuristics
described in the Microsoft paper, so for a font to work it needs to declare the
naming that would be produced by this heuristic directly
Is this a bug in the font, which I should be asking them to fix
just something we don't really cope with very well?
If upstream wants its font to work with Linux they need to change the font yes.
However it may break compatibility with old windows versions and old windows
apps. What confuses fontconfig is probably the info added to make those apps
understand those fonts.
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.