From Fedora Project Wiki
< Changes
(explain upgrades more clearly) |
m (Add BZ) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 54: | Line 54: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1600675 #1600675] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 198: | Line 198: | ||
== User Experience == | == User Experience == | ||
Users will see better quality of | Users will see better quality and variety of fonts for CJK characters rendered on applications and desktops. | ||
<!-- If this change proposal is noticeable by users, how will their experiences change as a result? | <!-- If this change proposal is noticeable by users, how will their experiences change as a result? | ||
| Line 220: | Line 220: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) | * Contingency mechanism: (What to do? Who will do it?) Revert all of changes in packages and comps <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: Beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: Beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 237: | Line 237: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
The default fonts for Chinese, Japanese, and Korean have been changed to Noto fonts providing consistent Sans, Serif and Mono typefaces. | |||
[[Category: | [[Category:ChangeAcceptedF29]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 18:33, 12 July 2018
CJK Default Fonts To Noto
Summary
Changes the default fonts for Chinese, Japanese, and Korean (CJK) languages to Google Noto.
Owner
- Name: Akira TAGOH, Peng Wu
- Email: tagoh@redhat.com, pwu@redhat.com
- Release notes owner:
Current status
Detailed Description
This proposal is to change the default fonts for CJK languages to Google Noto and adopts OpenType Collection format to suppress disk space increase as far as possible. Typefaces mapping will change as follows:
| Language / f28 | Sans-serif | Serif | Monospace |
|---|---|---|---|
| ja | VL Gothic | VL Gothic | VL Gothic |
| ko | NanumGothic | NanumGothic | NanumGothic |
| zh-CN | Source Han Sans CN | Source Han Serif CN | Source Han Sans CN |
| zh-TW | Source Han Sans TW | Source Han Serif TW | Source Han Sans TW |
where the italics means the font is a substitute not actually providing the correct face.
| Language / f29 | Sans-serif | Serif | Monospace |
|---|---|---|---|
| ja | Noto Sans CJK JP | Noto Serif CJK JP | Noto Sans Mono CJK JP |
| ko | Noto Sans CJK KR | Noto Serif CJK KR | Noto Sans Mono CJK KR |
| zh-CN | Noto Sans CJK SC | Noto Serif CJK SC | Noto Sans Mono CJK SC |
| zh-TW | Noto Sans CJK TC | Noto Serif CJK TC | Noto Sans Mono CJK TC |
Note that all CJK fonts will be unified into one OpenType Collection format file per weight-variant so only the total size for CJK is given for F29. The disk space is calculated from the font file sizes:
| \ | ja | ko | zh-CN | zh-TW | Total |
|---|---|---|---|---|---|
| f28 | 3.9M | 13.8M | 133.1M | 77.4M | 228.2M |
| f29 | - | - | - | - | 288M |
Benefit to Fedora
This change will provides better quality of rendering for all of CJK characters. We will now have default installed Serif face for Japanese and Korean, and also a Monospace face for all of CJK languages and keep consistencies in look among those typefaces.
Scope
- Proposal owners:
- Update CJK fonts packages with the proper priority of fontconfig config files
- Update fonts group in comps [done]
- Other developers:
- For application package maintainers:
- Any GUI applications that don't support TTC or OTC, would need to be fixed.
- For application package maintainers:
- Release engineering: #7592 (a check of an impact with Release Engineering is needed)
- List of deliverables: All of the installable images should be affected
- Policies and guidelines: N/A
- Trademark approval: N/A
Upgrade/compatibility impact
Existing users upgrading should be unaffected, and will still have the same old default CJK fonts on their system by default. So there will be no need to modify any font configuration files by the hand. However users are encouraged to install the new improved fonts after upgrading like this:
# dnf install google-noto-sans-cjk-ttc-fonts google-noto-serif-cjk-ttc-fonts
How To Test
- Check if the default font is changed to Noto:
- ja
- LANG=ja_JP.UTF-8 fc-match sans-serif:lang=ja
- LANG=ja_JP.UTF-8 fc-match serif:lang=ja
- LANG=ja_JP.UTF-8 fc-match monospace:lang=ja
- ko
- LANG=ko_KR.UTF-8 fc-match sans-serif:lang=ko
- LANG=ko_KR.UTF-8 fc-match serif:lang=ko
- LANG=ko_KR.UTF-8 fc-match monospace:lang=ko
- zh-cn
- LANG=zh_CN.UTF-8 fc-match sans-serif:lang=zh-cn
- LANG=zh_CN.UTF-8 fc-match serif:lang=zh-cn
- LANG=zh_CN.UTF-8 fc-match monospace:lang=zh-cn
- zh-tw
- LANG=zh_TW.UTF-8 fc-match sans-serif:lang=zh-tw
- LANG=zh_TW.UTF-8 fc-match serif:lang=zh-tw
- LANG=zh_TW.UTF-8 fc-match monospace:lang=zh-tw
- ja
- Check the following items on applications (GTK+: gedit, gnome-terminal etc, Qt: kate, konsole etc, X/Xft: xterm etc, Others: LibreOffice, firefox etc)
- Check applications preference if the above fonts are visible
- Check applications if the above fonts are rendered properly
- Check applications if those fonts are chosen as the default font for certain language when the generic family names like sans-serif, serif, and monospace is selected.
- See the above table for mapping between language and families
User Experience
Users will see better quality and variety of fonts for CJK characters rendered on applications and desktops.
Dependencies
N/A
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Revert all of changes in packages and comps
- Contingency deadline: Beta freeze
- Blocks release? No
Documentation
- What is the Google Noto CJK fonts?: https://www.google.com/get/noto/help/cjk/
- OpenType specification: https://docs.microsoft.com/en-us/typography/opentype/spec/
Release Notes
The default fonts for Chinese, Japanese, and Korean have been changed to Noto fonts providing consistent Sans, Serif and Mono typefaces.