Summary: | More metric compat fonts | ||
---|---|---|---|
Product: | fontconfig | Reporter: | Behdad Esfahbod <freedesktop> |
Component: | conf | Assignee: | Akira TAGOH <akira> |
Status: | RESOLVED FIXED | QA Contact: | Behdad Esfahbod <freedesktop> |
Severity: | normal | ||
Priority: | medium | CC: | akira, fontconfig-bugs, freedesktop |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Further changes to 30-metric-aliases.conf
Further changes to 30-metric-aliases.conf |
Description
Behdad Esfahbod
2013-08-20 14:55:18 UTC
Where is it from? and why do they wannt to remove an alias for Arial Narrow? From a bug on Chrome's font selection. That bug is irrelevant. Oh, the Arial Narrow my bad, I should have cut that part out. I just diff'ed it with our latest file. https://code.google.com/p/chromium/issues/detail?id=242046 Aha. interesting for binding stuff. though it's a known RFE as Bug#19375. Anyway, the change without Arial Narrow one committed into git. Created attachment 85795 [details] [review] Further changes to 30-metric-aliases.conf I'm not happy with the current 30-metric-fonts.conf. This patch makes some changes: Big changes: - Handle more PostScript fonts (further reduce 30-urw-aliases.conf) - Update the big comment Specific->Generic: - Add missing maps, for symmetry Generic<->Generic: - Add "Helvetica Condensed" <-> "Arial Narrow" map Generic->Specific: - Add missing Courier -> Cursor alias - Add "Helvetica Condensed" -> "Heros Cn" alias - Remove Arial -> Heros and "Times New Roman" -> Termes maps Reopening, please look at the posted patch. Thanks. Normally it's preferable to open new bugs, but this one should be fine. Created attachment 85796 [details] [review] Further changes to 30-metric-aliases.conf Just noticed I accidentally posted an old version. Whoops. Thanks. merged into git. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.