Last modified: 2014-07-16 20:18:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 63827 - Explore better Korean default fonts
Explore better Korean default fonts
Status: NEW
Product: MediaWiki skins
Classification: Unclassified
Vector (Other open bugs)
All All
: High normal
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks: typography-refresh 63942
  Show dependency treegraph
Reported: 2014-04-11 17:48 UTC by Jon
Modified: 2014-07-16 20:18 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Screenshot by original reporter (497.67 KB, image/jpeg)
2014-04-11 19:18 UTC, Nemo

Description Jon 2014-04-11 17:48:36 UTC
The typography refresh didn't help readers in Korean. Let's find a better font choice for those readers.


Copied from

Hello. I'm editor on Korean WP, and I saw your notice on our villiage pump.

As for Korean. There is good fonts for korean, which is distributed by Free copyright licences. For example, Nanum fonts(Nanum means 'share' in Korean), which is distributed by Open Font Licence 1.1. And these fonts shows better legibility than normal fonts like Gulim and Dotum. And Un fonts also serves in Open licences, but I think these fonts do not have good legibilities.

If this refresh project supports multiple selection of fonts, How's about Include Nanum fonts and some more open fonts in Wikimedia projects when using Korean? - Galadrien (talk) 12:42, 1 April 2014 (UTC)

Hi Galadrien. I think it would be fine to write in Korean Wikipedia Common.css to refer to a different open source font. But as the FAQ notes, we're not actually having users download new fonts, we're only telling their browsers which fonts to use, if they already have it. So unless most readers or editors on Korean Wikipedia would already have the font on their system, there may not be much point in changing it. As a side note, I am also curious: do you think the serif font for page titles and section headers is okay in Korean? I know non-Latin scripts may look different with serifs. Steven Walling (WMF) • talk 22:07, 2 April 2014 (UTC)
Um.. It maybe good, but At this point, em-size of English font and Korean font is different- so you have to think how to make balance for English and numeral decender and Korean baseline.

And, especially, printed materials in South Korea(And CJK printing culture also) do not uses serif fonts for main subject- they usually use san-serif as subject, then use serif for main contents. So you can make think about make changes for CJK languages. - Galadrien (talk) 02:52, 4 <april> 2014 (UTC)

I uploaded the sample of 'problems' in my wiki. Please check the circles especially. - Galadrien (talk) 03:05, 4 <april> 2014 (UTC)

위키백과:사랑방 (기술)/2014년 4월#문서 제목 서체에 대해 also talking about this problems. - Galadrien (talk) 03:16, 4 <april> 2014 (UTC)
Comment 1 Nemo 2014-04-11 19:18:54 UTC
Created attachment 15083 [details]
Screenshot by original reporter
Comment 2 Revi 2014-07-16 08:29:05 UTC
Google and Adobe published[1] Apache-licensed CJK font[2]. Maybe this could be used?

Comment 3 Steven Walling 2014-07-16 20:18:48 UTC
(In reply to Revi from comment #2)
> Google and Adobe published[1] Apache-licensed CJK font[2]. Maybe this could
> be used?
> [1]:
> html
> [2]:

This fonts are quite nice, but would require us to deliver a webfont. For now we're still sticking to the requirement that we are not delivering additional fonts to users, though this could change in the future.

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