-
Notifications
You must be signed in to change notification settings - Fork 1.3k
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
一些關於思源黑體的建議(2021年8月4日) #305
Comments
|
菩薩慈悲:請多禮聘、請教一些真正有名有姓有頭有臉專家學者的意見吧。不要都是一些化名、暱稱的無名氏、沒品牌、不負責任,像路邊攤、沒實體店面、到時無法追究的關起門來自己幹、閉門造車、師心自用的伙伴。且參與者當如功德碑、四庫館臣題名職官一樣,具名負責以示後世才好。 |
|
吾所師者皆真人也,非子所謂閉門造車、師心自用者。思源黑體、宋體,字庫已滿,凡陸萬伍仟伍佰叁拾陸形,不減不能增新,不損不能益民。 |
Then we shall extend the supported range to U+3400-4DBF, 4E00-9FFF, 20000-2FFFC. |
就第3項,這牽涉到思源字體目的問題。按個人理解,思源字體的目的是為了創造適合不同地區使用並風格相同的字體,從而方便互相組合使用。非官方支持,並在其他名義下分發的字體,並不能取代這角色。 就第12項,我認為要達到這目的,首要是讓電腦系統能區別並調用舊字形,Adobe和Google及其他造字廠商才會有動力去支持。為了讓電腦系統區別和調用舊字形,個人認為其中一個可行方案,是在ISO 15924 文字系統代號國際標準中,像繁體中文=Hant、簡體中文=Hans一般,加入代表舊字形文字系統的代號。但個人在漢字方面並非專家,無力代表全球漢字使用者向有關當局提供相關資料以申請相關代號。如果這裡有更適任者的話,希望能代為提出相關申請。 |
舊字形文字系統屬於漢字(Hani)、繁體中文(Hant),參考《傳承字形部件檢校表》《傳承字形筆畫表》《傳承字型推薦形體表》。 |
就像Hant屬於Hani但依然有自己的代碼一樣,為方便使用舊字型而申請新代碼使用應該沒問題? |
If you add a new script code, then you also need to define a way to activate it through OpenType. OpenType currently uses hani with ZHH, ZHT and ZHTM, hant and hans are not used. |
In other words, it is also necessary to apply for a "Language system tags"
in OpenType Layout Tag Registry to Microsoft
https://docs.microsoft.com/en-us/typography/opentype/spec/languagetags
But how to file such application?
在 2021年8月18日週三 17:22,Henry Chan ***@***.***> 寫道:
… If you add a new script code, then you also need to define a way to
activate it through OpenType. OpenType currently uses hani with ZHH, ZHT
and ZHTM, hant and hans are not used.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALUMLKSRMMBGLHPESE5MULT5N3WVANCNFSM5BQB6ULQ>
.
|
I see most of these posts are a call to either return to or add traditional orthographic forms similar to JP and KR for TC, but they already discussed this before, even as recently as 2020, and as much as I don't like 楷化 (handwritten style for sans serif) too, to summarise from this link I've given (which included a lot of heated arguments), Adobe's project scope is to comply with national government standards, to meet other user needs which require these kind of glyph shapes, and Adobe already said it's way beyond their scope. There's nothing stopping one from picking the JP or KR locale for Chinese use. In addition, this project has a technical limit of 65536 glyphs and Adobe wants one super font with many locales included for convenience, and finally, there is a character coverage limit for each locale due to this technical limit, maybe OP was also calling for traditional orthography coverage for all of the Unicode CJK blocks, which is too much of a labour to do when one (even well resourced) has potentially hundreds of thousands of Chinese characters in hand, way more than the 65536 glyph limit in a single font. Furthermore, there are SHS forks (and maybe more to come) which for the time being meet this kind of traditional orthography need despite being unofficial and imperfect. I recommend this issue be closed. Unless there's something else I missed, but isn't Source Han Sans also supporting OpenType locale already? |
OK. See Adobe Ming and Adobe Fan Heiti which helps. |
Prerequisites
Description
[Please provide here a thorough description of the issue, being sure to specify at least a Unicode code point if it affects a character or a particular glyph for a character. Including the character itself after the Unicode code point also helps, for visual reasons. Images with annotations that pinpoint the issue also help. If you are referencing standards, please keep in mind that they may have known or unknown errors. It is not necessary to provide CIDs.]
The text was updated successfully, but these errors were encountered: