Bug 864781 - nanum-gothic-coding fonts 2.0 released
Summary: nanum-gothic-coding fonts 2.0 released
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nhn-nanum-gothic-coding-fonts
Version: 18
Hardware: noarch
OS: Linux
unspecified
medium
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:10 UTC by sangu
Modified: 2012-10-29 01:17 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description sangu 2012-10-10 06:10:54 UTC
Description of problem:
A long while ago,
http://ftp.de.debian.org/debian/pool/main/f/fonts-nanum-coding/fonts-nanum-coding_2.0.orig.tar.gz or 

http://dev.naver.com/projects/nanumfont/download

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

How reproducible:


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


Expected results:


Additional info:

Comment 1 Fedora Update System 2012-10-10 07:50:01 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:06:45 UTC
Thanks! this package works well

Comment 3 Fedora Update System 2012-10-10 18:06:22 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:17:13 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.