From Fedora Project Wiki
Line 17: Line 17:
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 
-->
 
-->
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
  
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
Line 80: Line 78:
 
<!-- 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/issue/7224 #7224] (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/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 -->
 
<!-- 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 -->

Revision as of 08:27, 17 January 2018


Chinese Default Fonts to Google Noto

Summary

Changes the default fonts for Chinese to Google Noto.

Owner

  • Name: Peng Wu
  • Email: pwu@redhat.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 28
  • Last updated: 2018-01-17
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Changes the default fonts for Chinese to Google Noto. each typefaces will be changed as the following:

  • sans-serif
    • Source Han Sans -> Noto Sans CJK
  • serif
    • Source Han Serif -> Noto Serif CJK
  • monospace
    • Source Han Sans -> Noto Sans Mono CJK


Benefit to Fedora

This changes provides better quality of rendering for Chinese characters and consistencies in look among typefaces.

Scope

  • Proposal owners:
    • Update packages with the proper priority of fontconfig config file (adobe-source-han-*-fonts, google-cjk-noto-*-sc-fonts and google-cjk-noto-*-tc-fonts)
    • Update comps
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

  • Check if the default font is changed to Noto
    • run fc-match for sans, serif, and monospace say
  • Check applications, including desktop/toolkit specific and terminals if Chinese characters is properly rendered.

User Experience

will see better quality of rendering for Chinese characters on applications and on desktops.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), No
  • Blocks product? none

Documentation

N/A (not a System Wide Change)

Release Notes