From Fedora Project Wiki
Line 167: Line 167:
  
 
<!-- 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?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Contingency mechanism: (What to do?  Who will do it?) We can simply revert the relevant changes to what we had before this change <!-- 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: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
+
<!-- * Blocks product? product --><!-- Applicable for Changes that blocks specific product release/Fedora.next -->
  
 
== Documentation ==
 
== Documentation ==

Revision as of 12:45, 16 July 2019


Default Variable Fonts In Noto

Summary

This Change aims to change the priority in Google Noto to make Variable Fonts higher than non-Variable Fonts.


Owner

Current status

  • Targeted release: Fedora 31
  • Last updated: 2019-07-16
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The font selection to match better fonts mostly depends on the order of the configuration files for fontconfig under /etc/fonts/conf.d as long as it is written according to the templates in our guidelines. we usually change the priority of it to choose which fonts are used for certain languages.

This proposal is to give Variable fonts version of Google Noto families the priority more than non-Variable fonts in Google Noto families.

Benefit to Fedora

The variable fonts of Google Noto families supports some axes for variations into one OpenType font file. no need to have multiple files per variations. this saves disk spaces and give us more better experience.

We have already enabled Google Noto as default fonts for Sinhala which affects by this change. it may be good to have the comparison table how it saves.

Language non-VF VF
Sinhala 10.94MiB 1.02MiB

Scope

  • Proposal owners:
    • Update google-noto-fonts package to change the priority of fontconfig configuration files
    • Update langpacks to replace non-VF to VF version of packages
    • Update comps.xml to replace non-VF to VF version of packages
  • 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

N/A (not a System Wide Change)

User Experience

Users can see more variations of fonts if applications supports.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) We can simply revert the relevant changes to what we had before this change
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? No

Documentation

N/A (not a System Wide Change)

Release Notes