(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 115: | Line 115: | ||
<!-- 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?) | * Contingency mechanism: (What to do? Who will do it?) Will drop patches from icu and glibc. | ||
<!-- 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: | * Contingency deadline: Before F23 Beta release eg. Beta freeze. | ||
<!-- 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? | * Blocks release? No | ||
* Blocks product? product | * Blocks product? product No | ||
== Documentation == | == Documentation == | ||
Revision as of 08:40, 22 June 2015
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Unicode 8.0 support
We are updating Glibc Unicode data from Unicode 5.1 to Unicode 7.0 version. It took a long time, since there was not much documentation on how to update Unicode data and also there was the chance of loosing backward compatibility. Most of the issues are resolved now and patches are ready for inclusion. This update adds around 8000 supported characters in Glibc, and also corrects the Unicode data of many characters per the latest Unicode standard.
Owner
- Name: Mike Fabian Pravin Satpute Siddhesh Poyarekar
- Email: mfabian At redhat DOT com, pravins At fedoraproject DOT org, spoyarek AT redhat DOT com
- Release notes owner:
Current status
- Targeted release: Fedora 23
- Last updated: 22 Jun 2015
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Unicode 8.0 got release on 17th June 2015. It includes 41 new emoji characters (including five modifiers for diversity), 5,771 new ideographs for Chinese, Japanese, and Korean, the new Georgian lari currency symbol, and 86 lowercase Cherokee syllables. It also adds letters to existing scripts to support Arwi (the Tamil language written in the Arabic script), the Ik language in Uganda, Kulango in the Côte d’Ivoire, and other languages of Africa. In total, this version adds 7,716 new characters and six new scripts.
To get support for these characters in Fedora we will need updates to core libraries Glibc and Lib ICU. We are planning to update our core libraries Glibc and Lib ICU with the help of upstream.
"Update locale data to Unicode 8.0" https://sourceware.org/bugzilla/show_bug.cgi?id=18568
Benefit to Fedora
With this change, users and developers of Fedora will get Unicode 8.0 support through core libraries. Users will get an updated Unicode data from locales. No new functionality is added. Fedora is the leading distribution when it comes to internationalization. By including this change, Fedora users and developers will get the Unicode 8.0 support exactly on the time.
Scope
- Proposal owners: Work with upstream and file bugs and provide patches where required.
- Other developers: This change will impact glibc, ICU and all applications that uses these libraries. Other Developers do not need to make any changes from their end, but they need to watch how their application behaves with improved localedata. We need proper testing to see that it does not break any application.
- Release engineering: No work required from Release engineering.
- Policies and guidelines: No, this change does not required any updates to Policies or packaging guideline updates.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Upgrade will be smooth. Users will get exact things with updated Unicode data.
N/A (not a System Wide Change)
How To Test
- Glibc includes extensive test-case coverage to test localedata changes.
- This change is affecting Unicode characters, so users will notice little effect on rendering if any.
- Glibc is used by rendering engine for determining the type of characters, so again observe rendering and report if any issue.
- Document section provide detailed report regarding change.
User Experience
Users and Developers will get support for Unicode standard 8.0 through locales.
Dependencies
- Upstream release schedule.
- If our patches does not come in upstream, we will try to patch it in Fedora.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Will drop patches from icu and glibc.
- Contingency deadline: Before F23 Beta release eg. Beta freeze.
- Blocks release? No
- Blocks product? product No
Documentation
N/A (not a System Wide Change)