From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...")
 
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 
 
 
<!-- Self Contained or System Wide Change Proposal?
 
<!-- Self Contained or System Wide Change Proposal?
 
Use this guide to determine to which category your proposed change belongs to.
 
Use this guide to determine to which category your proposed change belongs to.
Line 21: 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 -->
  
= Change Proposal Name <!-- The name of your change proposal --> =
+
= Convert Bitmap Font <!-- The name of your change proposal --> =
  
 
== Summary ==
 
== Summary ==
 
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.  
 
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.  
 
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". -->
 
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". -->
 +
This proposal plans to start converting the bitmap fonts in Fedora from legacy BDF/PCF format to modern OpenType format.
  
 
== Owner ==
 
== Owner ==
Line 32: Line 31:
 
This should link to your home wiki page so we know who you are.  
 
This should link to your home wiki page so we know who you are.  
 
-->
 
-->
* Name: [[User:FASAcountName| Your Name]]
+
* Name: [[User:pwu| Peng Wu]]
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
+
* Email: pwu@redhat.com
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 44: Line 43:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/32 | Fedora 32 ]]  
 
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
 
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 59: Line 58:
  
 
<!-- 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. -->
 +
 +
In Fedora 31, pango has been upgraded to 1.44, and switch to use harfbuzz library.
 +
 +
But harfbuzz doesn't support bitmap fonts or Adobe Type 1 fonts.
 +
In gnome-terminal, the bitmap fonts can't be used.
 +
 +
In order to use the bitmap fonts with pango 1.44.
 +
We propose to convert the bitmap fonts to OpenType fonts by fonttosfnt tool.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 89: Line 96:
 
     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 
     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 
-->
 
-->
 +
 +
Some bitmap fonts are used by many users.
 +
 +
After converted the bitmap fonts, users can continue to use the bitmap fonts in gnome-terminal, etc.
  
 
== Scope ==
 
== Scope ==
* Proposal owners:
+
* Proposal owners: Fonts SIG
 
<!-- 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: X.Org Maintainers <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 +
** Need to update the fonttosfnt tool in the xorg-x11-font-utils package.
 
<!-- 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?-->
  
Line 101: Line 113:
 
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 -->
  
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Policies and guidelines: Fonts Policy <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- 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 111: Line 123:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
+
 
 +
It depends on how we package the converted OpenType fonts.
 +
 
 +
* If we keep the converted OpenType fonts or both fonts in the same package, the upgrade path is simple.
 +
* If we introduce new sub package for bitmap fonts or OpenType fonts, the upgrade path need to be considered.
 +
** One possible solution for upgrade is to include the converted OpenType fonts in the original package, but provide the bitmap fonts in some compatibility package.
  
 
== How To Test ==
 
== How To Test ==
Line 129: Line 146:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
+
 
 +
# Install the converted OpenType bitmap fonts.
 +
# Check whether the converted bitmap fonts is listed in gnome-terminal, gedit, etc.
 +
# Compare the font rendering with Fedora 30, the converted fonts should look similar with the original bitmap fonts.
  
 
== User Experience ==
 
== User Experience ==
Line 142: Line 162:
 
  - 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.
 
-->
 
-->
 +
 +
After converting the bitmap fonts, terminal users will be able to use the new OpenType Bitmap font again with pango 1.44 in gnome-terminal, etc.
 +
 +
The converted bitmap fonts should have the similar shape for each glyph.
  
 
== Dependencies ==
 
== Dependencies ==
Line 147: Line 171:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
+
 
 +
Update the fonttosfnt package in xorg-x11-font-utils, which is the needed tool for bitmap font conversion.
 +
 
 +
And we plan to pick 5-10 most popular bitmap fonts for conversion.
 +
 
 +
We will try to find the better way for the conversion, then update more bitmap fonts in later updates or next Fedora release.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
  
 
<!-- 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: Fonts SIG will revert the changed 5-10 bitmap font packages. <!-- 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: Beta Freeze <!-- 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 -->
  
Line 163: Line 192:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
+
This change will enable Fedora 32 to use bitmap fonts with pango 1.44 again.
  
 
== Release Notes ==
 
== Release Notes ==
Line 171: Line 200:
 
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.  
 
-->
 
-->
 +
 +
In Fedora 32, we provide bitmap fonts with modern font format (OpenType Bitmap Font) to use with gnome-terminal and other applications which uses pango for font rendering.
  
 
[[Category:ChangePageIncomplete]]
 
[[Category:ChangePageIncomplete]]
Line 179: Line 210:
  
 
<!-- Select proper category, default is Self Contained Change -->
 
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
+
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SystemWideChange]] -->
+
[[Category:SystemWideChange]]

Revision as of 08:17, 24 December 2019


Convert Bitmap Font

Summary

This proposal plans to start converting the bitmap fonts in Fedora from legacy BDF/PCF format to modern OpenType format.

Owner

Current status

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

Detailed Description

In Fedora 31, pango has been upgraded to 1.44, and switch to use harfbuzz library.

But harfbuzz doesn't support bitmap fonts or Adobe Type 1 fonts. In gnome-terminal, the bitmap fonts can't be used.

In order to use the bitmap fonts with pango 1.44. We propose to convert the bitmap fonts to OpenType fonts by fonttosfnt tool.

Benefit to Fedora

Some bitmap fonts are used by many users.

After converted the bitmap fonts, users can continue to use the bitmap fonts in gnome-terminal, etc.

Scope

  • Proposal owners: Fonts SIG
  • Other developers: X.Org Maintainers
    • Need to update the fonttosfnt tool in the xorg-x11-font-utils package.
  • Policies and guidelines: Fonts Policy
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

It depends on how we package the converted OpenType fonts.

  • If we keep the converted OpenType fonts or both fonts in the same package, the upgrade path is simple.
  • If we introduce new sub package for bitmap fonts or OpenType fonts, the upgrade path need to be considered.
    • One possible solution for upgrade is to include the converted OpenType fonts in the original package, but provide the bitmap fonts in some compatibility package.

How To Test

  1. Install the converted OpenType bitmap fonts.
  2. Check whether the converted bitmap fonts is listed in gnome-terminal, gedit, etc.
  3. Compare the font rendering with Fedora 30, the converted fonts should look similar with the original bitmap fonts.

User Experience

After converting the bitmap fonts, terminal users will be able to use the new OpenType Bitmap font again with pango 1.44 in gnome-terminal, etc.

The converted bitmap fonts should have the similar shape for each glyph.

Dependencies

Update the fonttosfnt package in xorg-x11-font-utils, which is the needed tool for bitmap font conversion.

And we plan to pick 5-10 most popular bitmap fonts for conversion.

We will try to find the better way for the conversion, then update more bitmap fonts in later updates or next Fedora release.

Contingency Plan

  • Contingency mechanism: Fonts SIG will revert the changed 5-10 bitmap font packages.
  • Contingency deadline: Beta Freeze
  • Blocks release? No
  • Blocks product? product

Documentation

This change will enable Fedora 32 to use bitmap fonts with pango 1.44 again.

Release Notes

In Fedora 32, we provide bitmap fonts with modern font format (OpenType Bitmap Font) to use with gnome-terminal and other applications which uses pango for font rendering.