Bug 864778 - Wrong family in fontconfig config file
Summary: Wrong family in fontconfig config file
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nhn-nanum-gothic-coding-fonts
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-10 06:02 UTC by sangu
Modified: 2012-10-29 01:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-29 01:16:29 UTC
Type: Bug


Attachments (Terms of Use)

Description sangu 2012-10-10 06:02:37 UTC
Description of problem:
in /usr/share/fontconfig/conf.avail/65-3-nhn-nanum-gothic-coding.conf
sans-serif isn't.
monospace is right.


Version-Release number of selected component (if applicable):
1.500-4.fc18.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Fedora Update System 2012-10-10 07:49:53 UTC
nhn-nanum-gothic-coding-fonts-2.000-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/nhn-nanum-gothic-coding-fonts-2.000-1.fc18

Comment 2 sangu 2012-10-10 08:04:30 UTC
Thanks!
And after Updating to this package, bug 428389 was fixed.

Comment 3 Fedora Update System 2012-10-10 18:06:13 UTC
Package nhn-nanum-gothic-coding-fonts-2.000-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nhn-nanum-gothic-coding-fonts-2.000-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15797/nhn-nanum-gothic-coding-fonts-2.000-1.fc18
then log in and leave karma (feedback).

Comment 4 Daiki Ueno 2012-10-29 01:16:29 UTC
Closing, as the fix is now in stable.


Note You need to log in before you can comment on or make changes to this bug.