From Fedora Project Wiki
m (trivial update)
m (Add BZ)
 
(36 intermediate revisions by 4 users not shown)
Line 24: Line 24:


== Summary ==
== Summary ==
Changes the default fonts for CJK to Google Noto.
Changes the default fonts for Chinese, Japanese, and Korean (CJK) languages to Google Noto.


== Owner ==
== Owner ==
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: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1600675 #1600675]


== Detailed Description ==
== Detailed Description ==
This proposal is to change the default fonts for CJK to Google Noto. typefaces and the size consumptions will be changed as the follow:
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:


{| class="wikitable"
{| class="wikitable"
|-
|-
! Language !! Sans-serif !! Serif !! Monospace
! Language / f28 !! Sans-serif !! Serif !! Monospace
|-
|-
| ja || VL Gothic -> Noto Sans CJK JP || (No default serif) -> Noto Serif CJK JP || VL Gothic -> Noto Sans Mono CJK JP
| ja || VL Gothic || ''VL Gothic'' || ''VL Gothic''
|-
|-
| ko || NanumGothic -> Noto Sans CJK KR || (No default serif) -> Noto Serif CJK KR || (No default monospace) -> Noto Sans Mono CJK KR
| ko || NanumGothic || ''NanumGothic'' || ''NanumGothic''
|-
|-
| zh-CN || Source Han Sans CN -> Noto Sans CJK SC || Source Han Serif CN -> Noto Serif CJK SC || Source Han Sans CN -> Noto Sans Mono CJK SC
| zh-CN || Source Han Sans CN || Source Han Serif CN || ''Source Han Sans CN''
|-
|-
| zh-TW || Source Han Sans TW -> Noto Sans CJK TC || Source Han Serif TW -> Noto Serif CJK TC || Source Han Sans TW -> Noto Sans Mono CJK TC
| 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.


Note that all CJK fonts will be unified into one OpenType collection format file per weight-variants so there are no detailed estimation for f29. all of CJK languages' fonts will be covered by one package. the size consumptions are calculated from the font file size:
{| class="wikitable"
|-
! 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:


{| class="wikitable"
{| class="wikitable"
Line 85: Line 99:


== Benefit to Fedora ==
== Benefit to Fedora ==
This change will provides better quality of rendering for all of CJK characters. we will have default serif and monospace fonts for Japanese and Korean and keep consistensies in look among those typefaces.
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.


<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
Line 117: Line 132:
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:
** Update packages with the proper priority of fontconfig config files.
** Update CJK fonts packages with the proper priority of fontconfig config files
** Update fonts group in comps
** Update fonts group in comps [done]
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers:
** For application package maintainers:
*** Any GUI applications that don't support TTC or OTC, would need to be fixed.
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/7592 #7592] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: All of the installable images should be affected
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->


* Policies and guidelines: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


Line 136: Line 153:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
This change will be done by installing the updated packages. no need to update/modify any configuration files by the hand. the sort of this change may has the objective preference. they can revert this by uninstalling font packages like this:
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:


<nowiki># dnf uninstall google-noto-sans-cjk-ttc-fonts google-noto-serif-cjk-ttc-fonts</nowiki>
    # dnf install google-noto-sans-cjk-ttc-fonts google-noto-serif-cjk-ttc-fonts


<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
Line 145: Line 162:
* Check if the default font is changed to Noto:
* Check if the default font is changed to Noto:
** ja
** ja
*** LANG=ja_JP.UTF-8 fc-match sans-serif
*** LANG=ja_JP.UTF-8 fc-match sans-serif:lang=ja
*** LANG=ja_JP.UTF-8 fc-match serif
*** LANG=ja_JP.UTF-8 fc-match serif:lang=ja
*** LANG=ja_JP.UTF-8 fc-match monospace
*** LANG=ja_JP.UTF-8 fc-match monospace:lang=ja
** ko
** ko
*** LANG=ko_KR.UTF-8 fc-match sans-serif
*** LANG=ko_KR.UTF-8 fc-match sans-serif:lang=ko
*** LANG=ko_KR.UTF-8 fc-match serif
*** LANG=ko_KR.UTF-8 fc-match serif:lang=ko
*** LANG=ko_KR.UTF-8 fc-match monospace
*** LANG=ko_KR.UTF-8 fc-match monospace:lang=ko
** zh-cn
** zh-cn
*** LANG=zh_CN.UTF-8 fc-match sans-serif
*** LANG=zh_CN.UTF-8 fc-match sans-serif:lang=zh-cn
*** LANG=zh_CN.UTF-8 fc-match serif
*** LANG=zh_CN.UTF-8 fc-match serif:lang=zh-cn
*** LANG=zh_CN.UTF-8 fc-match monospace
*** LANG=zh_CN.UTF-8 fc-match monospace:lang=zh-cn
** zh-tw
** zh-tw
*** LANG=zh_TW.UTF-8 fc-match sans-serif
*** LANG=zh_TW.UTF-8 fc-match sans-serif:lang=zh-tw
*** LANG=zh_TW.UTF-8 fc-match serif
*** LANG=zh_TW.UTF-8 fc-match serif:lang=zh-tw
*** LANG=zh_TW.UTF-8 fc-match monospace
*** LANG=zh_TW.UTF-8 fc-match monospace:lang=zh-tw
* Check applications if they render CJK characters with the expected fonts
* Check the following items on applications (GTK+: gedit, gnome-terminal etc, Qt: kate, konsole etc, X/Xft: xterm etc, Others: LibreOffice, firefox etc)
** GTK+ apps like gedit, gnome-terminal
** Check applications preference if the above fonts are visible
** Qt apps like kate, konsole
** Check applications if the above fonts are rendered properly
** X/Xft apps like xterm
** 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.
** Others like LibreOffice, firefox...
*** See the above table for mapping between language and families


<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
Line 181: Line 198:


== User Experience ==
== User Experience ==
Users will see better quality of rendering for CJK characters on applications and on desktops.
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 203: 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?) revert all of changes in packages and comps <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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 211: Line 228:


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
* 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/
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
Line 222: 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:ChangePageIncomplete]]
[[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

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.
  • Release engineering: #7592 (a check of an impact with Release Engineering is needed)
  • 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
  • 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

Release Notes

The default fonts for Chinese, Japanese, and Korean have been changed to Noto fonts providing consistent Sans, Serif and Mono typefaces.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/CJKDefaultFontsToNoto&oldid=522341"