Bug 367791 - remove 59-liberation-fonts.conf
Summary: remove 59-liberation-fonts.conf
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: liberation-fonts
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Caius Chance
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-06 01:20 UTC by Behdad Esfahbod
Modified: 2012-07-30 09:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-28 03:21:10 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Behdad Esfahbod 2007-11-06 01:20:17 UTC 
fontconfig-2.4.92-1 that I'm just building contains all the configuration done
in 59-liberation-fonts.conf, and much more to make liberation-fonts useful. 
Please remove that file for F9.
Comment 1 Caius Chance 2007-11-28 03:21:10 UTC 
Patched & built.
Comment 2 Pravin Satpute 2012-07-26 16:06:52 UTC 
As per latest font packaging guideline, i am adding fontconfig files now. Also want to add some hinting instructions for Liberation Mono.
Comment 3 Akira TAGOH 2012-07-27 01:40:53 UTC 
If it's the common case, maybe good to consider contributing the changes to fontconfig upstream perhaps.
Comment 4 Pravin Satpute 2012-07-27 10:55:24 UTC 
Those are very specific.
Basically added https://bugzilla.redhat.com/show_bug.cgi?id=842568#c3 in conf for mono.
Comment 5 Nicolas Mailhot 2012-07-27 12:14:19 UTC 
(In reply to comment #3)
> If it's the common case, maybe good to consider contributing the changes to
> fontconfig upstream perhaps.

Just IMHO, it's better when the fontconfig files are shipped with the font files themselves, and upstreamed font project side. This way the font project (which is supposed to know its font best) is in charge of fontconfig tweaking

At least, this is how it was done for dejavu.
Comment 6 Pravin Satpute 2012-07-30 09:11:08 UTC 
Thanks Nicholas, will follow it for now.
Note You need to log in before you can comment on or make changes to this bug.