Comments on: Introducing Source Han Sans: An open source Pan-CJK typeface https://blog.typekit.com/2014/07/15/introducing-source-han-sans/ News about Typekit Wed, 30 Jul 2014 18:47:54 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Dr. Ken Lunde https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4611 Wed, 30 Jul 2014 18:47:54 +0000 http://blog.typekit.com/?p=12543#comment-4611 )]]> In reply to ̲ℳ̲ℴى̲ℯى̲ (@Mosesofmason).

Good question.

There are at least three reasons:

1) Noto Sans proper has exactly two weights, Regular and Bold, which doesn’t really equal the seven weights of Source Han Sans and Noto Sans CJK.

2) Noto Sans CJK (and thus Source Han Sans) is designed to harmonize with the existing weights of both the Noto Sans and Roboto families. (Your question then might have been about including Roboto given that it has a broader weight range than Noto Sans.)

3) When orchestrated via font fallback whereby Noto Sans proper or Roboto is at the head, the Latin portions of Noto Sans CJK is effectively ignored. Including Source Sans as the Western portion allows the fonts to be used stand-alone.

(I still have a long-term hope that Google will consider using Source Sans in lieu of Noto Sans or Roboto. ☺)

]]>
By: ̲ℳ̲ℴى̲ℯى̲ (@Mosesofmason) https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4610 Wed, 30 Jul 2014 02:41:49 +0000 http://blog.typekit.com/?p=12543#comment-4610 Good but why the Latin part of Source Hans Sans (Noto Sans Chinese, Noto Sans Japanese and Noto Sans Korean at Google side) are not pairing with Noto Sans?

]]>
By: 我叫什么并不重要 https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4609 Wed, 23 Jul 2014 01:21:08 +0000 http://blog.typekit.com/?p=12543#comment-4609 非常好

]]>
By: Ken Lunde (小林剣) (@ken_lunde) https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4608 Tue, 22 Jul 2014 17:19:22 +0000 http://blog.typekit.com/?p=12543#comment-4608 In reply to Ash.

Given the examples you cited, I think that the answer is yes, mainly because of the way in which we defined the scope of Simplified versus Traditional Chinese. Simplified Chinese is based on GB 18030, which effectively means all URO and Extension A ideographs have Simplified Chinese forms that conform to China’s conventions. Traditional Chinese is split into Big Five, which follows the Taiwan MOE glyph standard, along with Hong Kong SCS, which also follows (for better or for worse) the Taiwan MOE glyph standard. This was done mainly for consistency, especially given that Hong Kong SCS is effectively an add-on to Big Five. This is the one area in which Source Han Sans is receiving some criticism, which may be deserved.

The best way to find out whether Source Han Sans fulfills your needs is to actually download and use them.

]]>
By: Ash https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4607 Sun, 20 Jul 2014 22:32:51 +0000 http://blog.typekit.com/?p=12543#comment-4607 Just curious if the differences in traditional characters between Mainland China vs. Taiwan and Hong Kong were taken into account. (and no, I don’t mean the differences between Simplified and Traditional). When books on the Mainland are printed in traditional Chinese (as a lot of books on Chinese paleography and on Old Chinese reconstruction are), they still use some glyphs which are different than what is typically used in Taiwan and Hong Kong. For instance, 夠, 吃, 才 are used in Taiwan and HK, while 喫, 够, 纔 are often in Mainland Chinese books that are printed in Traditional characters. Of course, within these 3 examples, only the 夠 vs. 够 pair is of concern for the font (but I would think there are more characters that just this one affected).

]]>
By: stcheng https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4606 Thu, 17 Jul 2014 21:40:37 +0000 http://blog.typekit.com/?p=12543#comment-4606 太有意思了

]]>
By: Nathan Parker https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4605 Thu, 17 Jul 2014 19:30:39 +0000 http://blog.typekit.com/?p=12543#comment-4605 Typo: Sounds “good”.

]]>
By: Nathan Parker https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4604 Thu, 17 Jul 2014 19:30:01 +0000 http://blog.typekit.com/?p=12543#comment-4604 In reply to Nathan Parker.

Sounds goos. I’ll check it out. Thanks!

]]>
By: Ken Lunde https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4603 Thu, 17 Jul 2014 17:29:42 +0000 http://blog.typekit.com/?p=12543#comment-4603 In reply to Nathan Parker.

If you have no use for the glyphs for CJK characters, you are much better served by Source Sans Pro, not Source Han Sans.

]]>
By: Weber Lin https://blog.typekit.com/2014/07/15/introducing-source-han-sans/#comment-4602 Thu, 17 Jul 2014 15:20:14 +0000 http://blog.typekit.com/?p=12543#comment-4602 Thank you all very much and happy 25th birthday! These fonts are absolutely beautiful and the quality is unprecedented in the open source world!

]]>