-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTF Version? #29
Comments
I didn't release OTF files In order to avoid confusing with choosing font file type. 故意不公開OTF是為了減少版本的混亂(還有name table衝突等問題)。 |
是因為我感覺與思源宋體相比,源樣明體的顯示效果有時會不清晰,有人告訴我這是 hinting 的方式不同導致的。 |
沒有錯。 |
感謝解答!還是希望可以釋出 OTF 版本,即使作為另一專案亦可。 |
另一個理由是為了forks,如果某個人想要自己改變這個字體系列,現在的情況還是不可能的,因為在使用自動化工具時,TTF版本的Bézier curves使得不可能做的。如果有OTF版的話,那麼forks也可以使用這個字體系列作為基礎,Shippori Antique/Mincho 也是這樣嘛。 |
那單純只是 Glow Sans 寫的工具如此,並不是 TTF 無法編輯。 |
@Marcus98T Not related to the current project, but I am now using redchenjs/source-han-serif-classic. You can check if this meet your needs. |
@ayaka14732 OK, I am aware of this SHS Classic thing, next thing I suppose I might need to produce a list of glyphs that need remapping to different CIDs so it's closer to 源樣明體, but I don't have the time now. Case closed regardless. |
Currently, only TTF version is available. However, considering that Source Han Serif itself is OTF, there can be an OTF version alongside the TTF version as well.
The text was updated successfully, but these errors were encountered: