From Fedora Project Wiki
m (Add trackers)
 
(20 intermediate revisions by 3 users not shown)
Line 19: Line 19:
 
<!-- 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 -->
  
= Default Variable Fonts In Noto <!-- The name of your change proposal --> =
+
= Variable Noto Fonts <!-- The name of your change proposal --> =
  
 
== Summary ==
 
== Summary ==
Line 53: Line 53:
 
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=1739976 #1739976]
* Release notes tracker: <will be assigned by the Wrangler>
+
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/374 #374]
  
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
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.
+
The font selection to match better fonts mostly depends on the order of the configuration files for fontconfig which is available at /etc/fonts/conf.d as long as it is written along the templates in our guidelines. so if we want to change that behavior for certain languages, we usually change the priority of it.
  
This proposal is to give Variable fonts version of Google Noto families the priority more than non-Variable fonts in Google Noto families.
+
This proposal is to give the variable fonts version of Google Noto families higher priority than non-variable fonts in Google Noto families, to enable the variable fonts in Google Noto.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 73: Line 73:
 
| Sinhala || 10.94MiB || 1.02MiB
 
| Sinhala || 10.94MiB || 1.02MiB
 
|}
 
|}
 +
 +
There are also the variable fonts available for other languages too but not default fonts for them. this will gives similar benefits for them as well if one install them instead of non-VF version of Noto:
 +
* sans-serif
 +
** Latin
 +
** Arabic
 +
** Armenian
 +
** Bengali
 +
** Canadian Aboriginal
 +
** Cham
 +
** Cherokee
 +
** Devanagari
 +
** Ethiopic
 +
** Georgian
 +
** Hebrew
 +
** Kannada
 +
** khmer
 +
** Lao
 +
** Malayalam
 +
** Myanmar
 +
** Tamil
 +
** Thaana
 +
** Thai
 +
* serif
 +
** Latin
 +
** Armenian
 +
** Ethiopic
 +
** Georgian
 +
** Gujarati
 +
** Gurmukhi
 +
** Hebrew
 +
** Kannada
 +
** Khmer
 +
** Lao
 +
** Myanmar
 +
** Tamil
 +
** Thai
 +
** Tibetan
 +
* monospace
 +
** Latin
 
<!-- 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 103: Line 142:
 
== Scope ==
 
== Scope ==
 
* Proposal owners:
 
* 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
 
<!-- 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?-->
  
Line 138: Line 180:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
To check if you use the variable fonts:
 +
 +
<pre>
 +
$ fc-match -f '%{file}' sans-serif:lang=si
 +
/usr/share/fonts/google-noto-vf/NotoSansSinhala-VF.ttf
 +
</pre>
  
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
The filename should be obvious for the variable fonts.
N/A (not a System Wide Change)
 
  
 
== User Experience ==
 
== User Experience ==
Line 153: Line 200:
 
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 
-->
 
-->
 +
Users can see more variations of fonts if applications supports.
  
 
== Dependencies ==
 
== Dependencies ==
Line 163: Line 211:
  
 
<!-- 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 ==
Line 183: Line 231:
 
-->
 
-->
  
[[Category:ChangePageIncomplete]]
+
<!-- [[Category:Change]] -->
 +
[[Category:ChangeAcceptedF31]]
 
<!-- 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 03:01, 12 August 2019


Variable Noto Fonts

Summary

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


Owner

Current status

Detailed Description

The font selection to match better fonts mostly depends on the order of the configuration files for fontconfig which is available at /etc/fonts/conf.d as long as it is written along the templates in our guidelines. so if we want to change that behavior for certain languages, we usually change the priority of it.

This proposal is to give the variable fonts version of Google Noto families higher priority than non-variable fonts in Google Noto families, to enable the variable fonts in Google Noto.

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

There are also the variable fonts available for other languages too but not default fonts for them. this will gives similar benefits for them as well if one install them instead of non-VF version of Noto:

  • sans-serif
    • Latin
    • Arabic
    • Armenian
    • Bengali
    • Canadian Aboriginal
    • Cham
    • Cherokee
    • Devanagari
    • Ethiopic
    • Georgian
    • Hebrew
    • Kannada
    • khmer
    • Lao
    • Malayalam
    • Myanmar
    • Tamil
    • Thaana
    • Thai
  • serif
    • Latin
    • Armenian
    • Ethiopic
    • Georgian
    • Gujarati
    • Gurmukhi
    • Hebrew
    • Kannada
    • Khmer
    • Lao
    • Myanmar
    • Tamil
    • Thai
    • Tibetan
  • monospace
    • Latin

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

To check if you use the variable fonts:

$ fc-match -f '%{file}' sans-serif:lang=si
/usr/share/fonts/google-noto-vf/NotoSansSinhala-VF.ttf

The filename should be obvious for the variable fonts.

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