TC版的Codepage是否設定為950會好些，如果有已區分TC/SC的話。

另外TC版在win10下的字體，按”中文(繁體)“篩選是找不到的，試一下“中文(簡體)”，或是“漢字”也沒有，建議已分別C(S/T) JK的話，可以再修補這部分，應會更完美的。

希望能用字體變形技術 把日本開源字體 m+ font 補齊

Concerning a very frequently used ideograph "的", there are two coherency problems:

• It does not match with, for example, 玓, whose design has a "㇐" instead of a "㇔" in the right component. I believe similar issues can be fixed with reference to the mapping mechanism of Genne Gothic, which maps not only KR glyphs but JP glyphs (with variant selector) also to achieve the so-called traditional printing shapes 印刷舊字形.
• A less urgent glitch. The left components do not align in the word 的皪. Though it's not a common word, it might be desirable to use contextual alternates to obtain a desired different design only in this word.

Even if it isn't this project's particular interest to provide traditional printing shapes I'd very much like to see a more coherent design!

你好！在下於字型論壇上分享大大這字體消息時，有壇友回報這個，希望代爲反映。

請反饋作者 繁體版中「斷」粗體中有瑕疵
因為無法聯繫作者 請幫忙反饋 繁體版中「斷」粗體中有瑕疵

辛苦了^^

I know you started with Genne Gothic as a base, but unfortunately I do not believe that the font has the full Kangxi glyphs. I also want to upstream some changes from SHS v2.001. Even though it is for 源樣黑體, the table also have Source Han Sans CID.

The 牙 radical has to follow that of 源樣黑體, not the KR form. I don't have the time to find the Unicode number and CID number for Source Han Sans.
Affected characters: "牙冴訝呀邪鴉雅芽穿". You need to dig into the hidden glyphs of Source Han Sans in order to get those glyphs.

The characters with 呈 need to be changed also. Affected characters are "呈程浧珵桯鋥聖檉".
Use the TW form: "呈程聖"
Use the JP form: "浧珵桯鋥檉"

Also the 青/靑, 清/淸, need to unify to the latter. Same with U+7BC0 節; need to use U+FA56 (Update: It's at SHS v2 CID: 58950) for the main codepoint. Details here: #22

More characters I want to switch here, should apply to this font also:
ButTaiwan/genyog-font#21
ButTaiwan/genyo-font#9

Add the U+32FF ㋿ SQUARE ERA NAME REIWA from Source Han Sans v2.001 as well.

Translation of Readme.md into Japanese seems to be not completed. If it is okay to translate English version into Japanese, I can contribute in translation because I can't understand Chinese language. Also, it's very happy for translators if you share the raw editable data of images used in Readme.md. Thanks.

请问能否将变形后的字体导出为otf

I created several aur packages based on the github release, if you guys want to maintain an official version of it, I'm happy to transfer ownership.

it seems to be base font weight dependent. in ExtLight weight, it happens when contrast < 0.77

在手机上用未来荧黑作显示字体，效果相当惊艳，比思源黑体的观感还更胜一筹。
如果能出 ttf 格式且带 hinting 的版本，对 Windows 会更友好，用作低 DPI 下的屏显字体将成为可能。
（PS：貌似 @be5invis 做过思源黑体的 hinting 版本，通过自动 hinting 加手工调参实现，不知道可否用作 hinting 其它字体的参考。）

For me, Regular (Weight 400) is a bit too "light" and Book (Weight 500) is a bit too "dark". I wonder if there is Weight 450 font?

System: Windows 10 build 1909 (Chinese (Simplified)), software: Microsoft Office 2016, build 12624 ver 2003

The styling of Welai Sans in Microsoft Office is weird and unpredictable. The main problem of the font is that all the weights of font is shown only under 1 name per width.

This caused that the same font is shown differently acrosss Microsoft Office.
Microsoft Word:

Microsoft Excel:

Microsoft PowerPoint:

My guess on the problem would be incorrect naming of name table. The following section is a ttx dump from GlowSansSC-Normal-ExtraBold.otf:

    <namerecord nameID="1" platformID="3" platEncID="1" langID="0x409">
      Glow Sans SC Normal
    </namerecord>
    <namerecord nameID="2" platformID="3" platEncID="1" langID="0x409">
      ExtraBold
    </namerecord>
   ...
    <namerecord nameID="1" platformID="3" platEncID="1" langID="0x804">
      未来荧黑 Normal
    </namerecord>
    <namerecord nameID="2" platformID="3" platEncID="1" langID="0x804">
      ExtraBold
    </namerecord>

The standard of naming scheme for name ID 1 and 2 is that name ID 1 contains the font family name + width + weight(except for regular, italic, bold, bold italic) and name ID 2 with the values Regular, Italic, Bold and Bold Italic only. Most software only detects name ID 1 which caused the problem above to occur. In the case of Microsoft Word, it uses the first font to be installed as the default font for family. Fixing the name table may fix this problem.

Thank you in advance.

如題，感謝大大製作這套字體。
大大未來有可能推出英數是以等寬字形為基底的版本嗎？

It would be a great addition.

当今屏显汉字边角都是直线的那种角。请务必考虑下，可以做个边角圆滑，但不是圆体。
我搜了下，满世界要么圆体，唯一搜到的思源柔黑是日本一家出的，但汉字不全。
我觉得。。。
我不要你觉得，我要我觉得，我觉得这个世界缺少这样柔感的字。特别需要。😁

可以参考下此项目https://github.com/cmiscm/leonsans
感觉还挺有趣的~

使用的Figma插件为Figma EX

hi,
想请问下未来荧黑字体是否可以买断版权？
我们想要买断的是以下几种：

Glow Sans SC Wide Light
Glow Sans SC Extended ExtraBold
Glow Sans SC Extended Medium
Glow Sans SC Normal Bold
Glow Sans SC Normal Regular

如果可以是否能帮忙提供买断细则和价格？谢谢！

0.91 版本 TC 字形有缺字，比如「教」、「值」、「清」、「填」等。

as titled

如图，“霞”、“葭”字会有误拔现象，“坝”、“八”、“扒”等字的笔画出现了问题。

Glow Sans SC Normal Bold，其他字重可能也会有这个问题。

可不可以增加可調圓角的效果？把所有尖角（包含筆畫拐彎處）都改成圓角？

SHS is released in opentype collections with glyphs shared across languages to reduce size. In theory, otfcc-ttcize would do the work for Glow Sans (and I've successfully used it for other fonts), but it conversely increased the total file size when I experimented with the Compressed Regular style of Glow Sans. It outputted a 32.8mb ttc, whereas J, SC, TC Compressed Regular otfs combined are about 27mb.

如题，这样就不用手动切换 Fira 了

I wonder if there is a plan to rebse this project to variable font version of Source Han Sans?

你好作者，謝謝你的努力。我正在面對無法順利安裝字體的問題。雙擊安裝後，它們顯示在我的Font book，但部份沒有出現在AI中的字體選單。依圖示，只有Normal出現在選項中。我嘗試重啟字體、軟件、電腦，但沒有任何改變。我正在使用ai2021，MacOS 11.5.2、GlowSansTC-v0.91。如我忽略了一些資訊，請指教。

FAQ里标注了“免费商用”，还需要获得开发团队的授权吗？

仅显示如图两种字形 请问如何解决

繁體中文字型細節小疏失
正確字型：
目前字型：

思源黑体的半角字符是偷懒直接压窄的，很不美观。
看到“基于思源黑体”就想是否终于有个字体修正了这个问题……但是没有（不妨对照ｴﾛエロ的横竖笔画）
我的意思是思源黑体的半角字符已经是废了，不能作为变形的基准原料。是否考虑用这样的算法直接从全角生成新的基准半角？我不懂程序，想问是否有这种可能性。

AI中一切正常，显示所有字重

我的Photoshop是最新版22.1.1，系统是macOS Big Sur

请教一个问题，samples下面的初始json（例如：SourceHanSansSC-Regular.json） 是怎么获得的呢，是通过otf转换过来的么（看数据的格式比较像otf）

It would help different users to package this font for different OS. Thanks.