From Fedora Project Wiki
 
(7 intermediate revisions by the same user not shown)
Line 68: Line 68:
 
So this Changes proposal aims to improve the user experience around font dependencies by replacing it to Langpacks instead. Langpacks contains various dependencies to use for certain languages, including dependencies for default fonts. so it will resolves the above issues.
 
So this Changes proposal aims to improve the user experience around font dependencies by replacing it to Langpacks instead. Langpacks contains various dependencies to use for certain languages, including dependencies for default fonts. so it will resolves the above issues.
  
 +
Specifically speaking, currently font dependency is generated like this:
 +
<pre>
 +
$ fc-query -f %{=pkgkit}  /usr/share/fonts/dejavu/DejaVuSans.ttf
 +
font(dejavusans)
 +
font(:lang=aa)
 +
font(:lang=ab)
 +
...
 +
</pre>
 +
 +
and at the build time, it is transformed to:<pre>
 +
Provides: font(dejavusans)
 +
Provides: font(:lang=aa)
 +
Provides: font(:lang=ab)
 +
...</pre>
 +
 +
After this proposal, the above result will be:
 +
<pre>
 +
Provides: font(dejavusans)
 +
</pre>
 +
 +
and then add `Provides: font(:lang=...)` line to corresponding sub-packages langpacks-core-*.
 +
 +
So asking for a font for a certain language through PackageKit will be achieved by langpacks-core-* instead of a random font package.
 
<!-- 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. -->
  
Line 103: Line 126:
 
* Proposal owners:
 
* Proposal owners:
 
** Update fontconfig to drop `font(:lang=...)` from the alias of the formatter for `%{=pkgkit}`
 
** Update fontconfig to drop `font(:lang=...)` from the alias of the formatter for `%{=pkgkit}`
** Add `font(:lang=...)` dependency to each `langpacks-core-...`
+
** Add a line of `Provides: font(:lang=...)` to each `langpacks-core-...`. for instance, `Provides: font(:lang=hi)` need to be added to `langpacks-core-hi`.
 
   
 
   
 
<!-- 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 110: Line 133:
 
<!-- 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] all of fonts packages must be rebuilt <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
+
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] all of fonts packages must be rebuilt so that the above change in fontconfig can be reflected to all of fonts packages. <!-- 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 -->
Line 123: Line 146:
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
The extra but the better fonts packages may be installed after upgrading.
+
Some packages may be installed after upgrading if corresponding langpacks-core-* packages isn't yet installed.
 
<!-- 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 142: Line 165:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
N/A
+
 
 +
# Check dependencies in langpacks-core-*. they must have corresponding `Provides: font(:lang=...)` line when asking with `rpm -q --provides`.
 +
# Check dependencies in fonts packages. they must contain no `Provides: font(:lang=...)` lines
  
 
== User Experience ==
 
== User Experience ==
Not too much changes in the user experience. they may see better fonts for certain language when they need to install a set of fonts for certain language support through PackageKit.
+
Users may see better fonts for certain language when they need to install a set of fonts for certain language support through PackageKit or package dependencies from others.
  
 
<!-- 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 193: Line 218:
  
 
<!-- Select proper category, default is Self Contained Change -->
 
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
+
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->
 

Latest revision as of 05:28, 27 December 2019


Font Dependencies to Langpacks

Summary

There are font(:lang=...) auto-generated dependency for fonts packages. it is used as a dependency identifier to satisfy a certain language requirement. but this way didn't guarantee qualities because what fonts packages is going to be pulled in is unreliable.

So this proposes to replace it with langpacks instead, which has proper dependencies for fonts and improve the user experience around fonts with applications.

Owner

  • Name: Akira TAGOH
  • Email: tagoh@redhat.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 32
  • Last updated: 2019-12-27
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The language based meta information about font dependency was introduced since Fedora 11. that was helpful to find out a font for missing glyphs through PackageKit and was useful for minority languages because we didn't have fonts packages for them so much. but the user experience wasn't that better under the certain condition.

Users can't predict what fonts will be installed. this may gives us worst result particularly when no fonts for the requested language is installed and/or is majority languages that has too many fonts such as English, because this logic doesn't guarantee the quality of fonts nor preferred fonts we expect to get installed by default. This random dependency sometimes introduces unexpected result too so that it's likely to happen that dependencies may be satisfied from external repositories. this may particularly be a problem when composing ISOs.

So this Changes proposal aims to improve the user experience around font dependencies by replacing it to Langpacks instead. Langpacks contains various dependencies to use for certain languages, including dependencies for default fonts. so it will resolves the above issues.

Specifically speaking, currently font dependency is generated like this:

$ fc-query -f %{=pkgkit}  /usr/share/fonts/dejavu/DejaVuSans.ttf
font(dejavusans)
font(:lang=aa)
font(:lang=ab)
...

and at the build time, it is transformed to:

Provides: font(dejavusans)
Provides: font(:lang=aa)
Provides: font(:lang=ab)
...

After this proposal, the above result will be:

Provides: font(dejavusans)

and then add Provides: font(:lang=...) line to corresponding sub-packages langpacks-core-*.

So asking for a font for a certain language through PackageKit will be achieved by langpacks-core-* instead of a random font package.

Benefit to Fedora

This proposal provides reliable, predictable, and consistencies in dependencies about fonts.

Scope

  • Proposal owners:
    • Update fontconfig to drop font(:lang=...) from the alias of the formatter for %{=pkgkit}
    • Add a line of Provides: font(:lang=...) to each langpacks-core-.... for instance, Provides: font(:lang=hi) need to be added to langpacks-core-hi.


  • Other developers: N/A
  • Policies and guidelines: N/A
  • Trademark approval: N/A

Upgrade/compatibility impact

Some packages may be installed after upgrading if corresponding langpacks-core-* packages isn't yet installed.


How To Test

  1. Check dependencies in langpacks-core-*. they must have corresponding Provides: font(:lang=...) line when asking with rpm -q --provides.
  2. Check dependencies in fonts packages. they must contain no Provides: font(:lang=...) lines

User Experience

Users may see better fonts for certain language when they need to install a set of fonts for certain language support through PackageKit or package dependencies from others.


Dependencies

  • fontconfig
  • langpacks

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Proposal owners will revert all of changes and rebuild all of fonts packages to add back deps
  • Contingency deadline: the beta freeze
  • Blocks release? No
  • Blocks product? N/A

Documentation

N/A

Release Notes