#sourcehanmono résultats de recherche
The forthcoming 216-font #SourceHanSans + #SourceHanSerif + #SourceHanMono + #NotoSansCJK + #NotoSerifCJK “Ultra OTC” is very space-efficient: although over 400MB in size, each 65,535-glyph #PanCJK font represents less than 2MB → github.com/adobe-fonts/so… #OpenSource
Version 1.002 of the 70-font #SourceHanMono Super OTC (OpenType/CFF Collection) was built and released today, which should behave better in GDI-based #Windows apps → github.com/adobe-fonts/so… #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 #OpenSource #PanCJK
その問題の理由を見つけました。直しますよ。ありがとう！ #SourceHanMono
Source Han Code JPとSource Han MonoでSの文字の大きさ(NTUSER.DATの部分)や、小文字nの形状が違うように感じるのですが、仕様でしょうか? 1枚目Source Han Mono 2枚目Source Han Code JP
#SourceHanMono Issue Template 4th Bullet: “Read the ReadMe (PDF) to better understand the scope of the project, to include the ‘Known Issues’ section at the very end. If you feel that your enhancement request is probably beyond the scope of this project, chances are it is.” 😈
The 143-font #SourceHan Mega OTC and 216-font Source Han + #NotoCJK Ultra OTC were also updated to reflect the #SourceHanMono Version 1.002 update → github.com/adobe-fonts/so…
The 70-font #SourceHanMono Super OTC is a little over 100MB. The total footprint of its 70 font instances, if they were installed as 70 separate OpenType/CFF fonts, would be over 1GB. I can also claim that the Super OTC deployment format literally decimates the footprint.
これ → “The total footprint of its 216 font instances, if they were installed as 216 separate OpenType/CFF fonts, would be nearly 4GB. I can therefore claim that the Ultra OTC deployment format literally decimates the footprint at approximately 400MB.”
#SourceHanMono Issue Template 3rd Bullet: “Thoroughly search the open and closed issues to avoid reporting a duplicate issue. If in doubt, search again.” 😉
#SourceHanMono Issue Template 2nd Bullet: “If you are requesting that region-specific subset OTFs or other deployment formats be produced, such as weight-specific OTCs, please make them yourself.” 🤔
From the “Changes” section on page 23 of the #SourceHanMono ReadMe file.
@ken_lunde Funny effect with #SourceHanMono ver. 1: any attempt to build a pdf from a docx document makes all horizontal advances, half-width kana and Lain included, to 1000. Version 1.002 fixes that
#SourceHanMono Issue Template 1st Bullet: “If you are reporting an issue that also affects #SourceHanSans from which Source Han Mono was derived, please report the issue there instead. If you do not, you are hereby warned that your issue will be closed with extreme prejudice.” 😈
For those who were not aware, I came up with the "Source Han" typeface name one afternoon in late-2013 or early 2014 while walking our German Shepherd, @LuckyLunde. #SourceHanSans #SourceHanSerif #SourceHanMono
The #OpenSource 70-font #SourceHanMono #PanCJK Super OTC (OpenType/CFF Collection) was just released → adobe.ly/2JC7TuK #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 @ryon106 @pauldhunt @hatchgogo
アドビの@ken_lundeが Source Han Code JP（源ノ角ゴシック Code JP）の等幅フォントのコンセプトをPanCJK版に拡大したSource Han Monoをリリースしました。adobe.ly/2JC7TuK github.com/adobe-fonts/so… #SourceHanMono
Version 1.001 of the 70-font #SourceHanMono Super OTC (OpenType/CFF Collection) was released today → adobe.ly/2JONv9K #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 #OpenSource #PanCJK
Source Han Monoは70フォントOTC版のみという巨大なフォントファミリーです。シンプルなJP版専用としてSource Han Code JPも引き続き公開していくつもりです。今後どのようにSource Han Code JPを展開していくかは検討中でございます。#SourceHanCodeJP #SourceHanMono
For those who were not aware, I came up with the "Source Han" typeface name one afternoon in late-2013 or early 2014 while walking our German Shepherd, @LuckyLunde. #SourceHanSans #SourceHanSerif #SourceHanMono
From the “Changes” section on page 23 of the #SourceHanMono ReadMe file.
@ken_lunde Funny effect with #SourceHanMono ver. 1: any attempt to build a pdf from a docx document makes all horizontal advances, half-width kana and Lain included, to 1000. Version 1.002 fixes that
@ken_lunde Funny effect with #SourceHanMono ver. 1: any attempt to build a pdf from a docx document makes all horizontal advances, half-width kana and Lain included, to 1000. Version 1.002 fixes that
The 143-font #SourceHan Mega OTC and 216-font Source Han + #NotoCJK Ultra OTC were also updated to reflect the #SourceHanMono Version 1.002 update → github.com/adobe-fonts/so…
Version 1.002 of the 70-font #SourceHanMono Super OTC (OpenType/CFF Collection) was built and released today, which should behave better in GDI-based #Windows apps → github.com/adobe-fonts/so… #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 #OpenSource #PanCJK
Version 1.001 of the 70-font #SourceHanMono Super OTC (OpenType/CFF Collection) was released today → adobe.ly/2JONv9K #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 #OpenSource #PanCJK
その問題の理由を見つけました。直しますよ。ありがとう！ #SourceHanMono
Source Han Code JPとSource Han MonoでSの文字の大きさ(NTUSER.DATの部分)や、小文字nの形状が違うように感じるのですが、仕様でしょうか? 1枚目Source Han Mono 2枚目Source Han Code JP
The 70-font #SourceHanMono Super OTC is a little over 100MB. The total footprint of its 70 font instances, if they were installed as 70 separate OpenType/CFF fonts, would be over 1GB. I can also claim that the Super OTC deployment format literally decimates the footprint.
これ → “The total footprint of its 216 font instances, if they were installed as 216 separate OpenType/CFF fonts, would be nearly 4GB. I can therefore claim that the Ultra OTC deployment format literally decimates the footprint at approximately 400MB.”
Source Han Monoは70フォントOTC版のみという巨大なフォントファミリーです。シンプルなJP版専用としてSource Han Code JPも引き続き公開していくつもりです。今後どのようにSource Han Code JPを展開していくかは検討中でございます。#SourceHanCodeJP #SourceHanMono
アドビの@ken_lundeが Source Han Code JP（源ノ角ゴシック Code JP）の等幅フォントのコンセプトをPanCJK版に拡大したSource Han Monoをリリースしました。adobe.ly/2JC7TuK github.com/adobe-fonts/so… #SourceHanMono
The #OpenSource 70-font #SourceHanMono #PanCJK Super OTC (OpenType/CFF Collection) was just released → adobe.ly/2JC7TuK #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 @ryon106 @pauldhunt @hatchgogo
The forthcoming 216-font #SourceHanSans + #SourceHanSerif + #SourceHanMono + #NotoSansCJK + #NotoSerifCJK “Ultra OTC” is very space-efficient: although over 400MB in size, each 65,535-glyph #PanCJK font represents less than 2MB → github.com/adobe-fonts/so… #OpenSource
#SourceHanMono Issue Template 2nd Bullet: “If you are requesting that region-specific subset OTFs or other deployment formats be produced, such as weight-specific OTCs, please make them yourself.” 🤔
#SourceHanMono Issue Template 4th Bullet: “Read the ReadMe (PDF) to better understand the scope of the project, to include the ‘Known Issues’ section at the very end. If you feel that your enhancement request is probably beyond the scope of this project, chances are it is.” 😈
The #OpenSource 70-font #SourceHanMono #PanCJK Super OTC (OpenType/CFF Collection) was just released → adobe.ly/2JC7TuK #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 @ryon106 @pauldhunt @hatchgogo
Version 1.002 of the 70-font #SourceHanMono Super OTC (OpenType/CFF Collection) was built and released today, which should behave better in GDI-based #Windows apps → github.com/adobe-fonts/so… #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 #OpenSource #PanCJK
Version 1.001 of the 70-font #SourceHanMono Super OTC (OpenType/CFF Collection) was released today → adobe.ly/2JONv9K #源ノ等幅 #본모노 #思源等宽 #思源等寬 #思源等寬_香港 #OpenSource #PanCJK
From the “Changes” section on page 23 of the #SourceHanMono ReadMe file.
@ken_lunde Funny effect with #SourceHanMono ver. 1: any attempt to build a pdf from a docx document makes all horizontal advances, half-width kana and Lain included, to 1000. Version 1.002 fixes that
Something went wrong.
Something went wrong.
United States Trends
- 1. April Fools N/A
- 2. Jose Fernandez N/A
- 3. #DaredevilBornAgain N/A
- 4. Max Fried N/A
- 5. CB Bucknor N/A
- 6. Megan N/A
- 7. #WWENXT N/A
- 8. Donovan Mitchell N/A
- 9. Jarrett Allen N/A
- 10. Cavs N/A
- 11. World Cup N/A
- 12. Max Muncy N/A
- 13. Knicks N/A
- 14. Stammen N/A
- 15. Lovelady N/A
- 16. Casey Mize N/A
- 17. #TamalesVsWaffles N/A
- 18. Angel Hernandez N/A
- 19. Italy N/A
- 20. Igor N/A