From Fedora Project Wiki
 
(23 intermediate revisions by 5 users not shown)
Line 25: Line 25:
== 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. -->
[http://blog.unicode.org/2016/06/announcing-unicode-standard-version-90.html Unicode 9.0] got released on 21th June 2016. Version 9.0 adds 7,500 characters, including six new scripts and 72 new emoji characters. These additions include six new scripts and 72 new emoji characters. These new script provide support for languages Osage, Nepal Bhasa, Fulani and other African languages, The Bravanese dialect of Swahili, used in Somalia, The Warsh orthography for Arabic and Tangut, a major historic script of China.
[http://blog.unicode.org/2016/06/announcing-unicode-standard-version-90.html Unicode 9.0] got released on 21th June 2016. Version 9.0 adds 7,500 characters, including six new scripts and 72 new emoji characters. These new script provide support for languages Osage, Nepal Bhasa, Fulani and other African languages, The Bravanese dialect of Swahili, used in Somalia, The Warsh orthography for Arabic and Tangut, a major historic script of China.


== Owner ==
== Owner ==
Line 45: Line 45:


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/25 | Fedora 25 ]]  
* 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 55: Line 55:
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=1357420 #1357420]
* Upstream patch for glibc submitted here: https://sourceware.org/ml/libc-alpha/2016-06/msg01258.html
* A glibc with that patch was pushed to rawhide on 2016-07-09
* Symbola font is already updated for Unicode 9.0 in rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=14808397 101 new characters have been added to this font.


== Detailed Description ==
== Detailed Description ==
Line 66: Line 69:
* libunistring - This portable C library implements Unicode string types in three flavours: (UTF-8, UTF-16, UTF-32), together with functions for character processing (names, classifications, properties) and functions for string processing (iteration, formatted output, width, word breaks, line breaks, normalization, case folding and regular expressions).
* libunistring - This portable C library implements Unicode string types in three flavours: (UTF-8, UTF-16, UTF-32), together with functions for character processing (names, classifications, properties) and functions for string processing (iteration, formatted output, width, word breaks, line breaks, normalization, case folding and regular expressions).
* Unicode UCD
* Unicode UCD
* glib2 Unicode data
* Fontconfig Update to CaseFolding.txt.


== Benefit to Fedora ==
== Benefit to Fedora ==
 
With this change, users and developers of Fedora will get Unicode 9.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 9.0 support exactly on the time.
    
    
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners: Work with upstream, file bugs and provide patches where required.
<!-- 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: 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.
<!-- REQUIRED FOR SYSTEM WIDE 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?-->
<!-- 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: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: No work required from Release engineering. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: No, this change does not required any updates to Policies or packaging guideline updates.  <!-- 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 96: Line 100:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
Upgrade will be smooth. Users will get same packages with an updated Unicode data.


== How To Test ==
== How To Test ==
Line 114: Line 118:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
* Characters added/changed in [https://pravins.fedorapeople.org/Changes-in-ucd-9 Unicode 9.0]
* 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 ==
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
Users and Developers will get support for Unicode standard 9.0 through locales.


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
* Upstream release schedule.
* If our patches does not come in upstream, we will try to patch it in Fedora. Though as per our upstream first policy we mostly avoid patching in Fedora.


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
== 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: Will move change to Fedora 26 release.
<!-- 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: Fedora 26 Beta release.
<!-- 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  
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? No


== Documentation ==
== Documentation ==
Line 141: Line 149:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
Will provide it later.


== Release Notes ==
== Release Notes ==
Line 150: Line 158:
-->
-->


[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF25]]
<!-- 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 -->
Line 157: Line 165:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SystemWideChange]] -->
[[Category:SystemWideChange]]

Latest revision as of 09:43, 30 September 2016


Unicode 9.0 support

Summary

Unicode 9.0 got released on 21th June 2016. Version 9.0 adds 7,500 characters, including six new scripts and 72 new emoji characters. These new script provide support for languages Osage, Nepal Bhasa, Fulani and other African languages, The Bravanese dialect of Swahili, used in Somalia, The Warsh orthography for Arabic and Tangut, a major historic script of China.

Owner

Current status

Detailed Description

We are upgrading core libraries in Fedora for Unicode 9.0

  • Updating Glibc localedata.
  • Updating Lib ICU. (If upstream releases well in time)
  • libunistring - This portable C library implements Unicode string types in three flavours: (UTF-8, UTF-16, UTF-32), together with functions for character processing (names, classifications, properties) and functions for string processing (iteration, formatted output, width, word breaks, line breaks, normalization, case folding and regular expressions).
  • Unicode UCD
  • glib2 Unicode data
  • Fontconfig Update to CaseFolding.txt.

Benefit to Fedora

With this change, users and developers of Fedora will get Unicode 9.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 9.0 support exactly on the time.

Scope

  • Proposal owners: Work with upstream, 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.
  • 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 same packages with an updated Unicode data.

How To Test

  • Characters added/changed in Unicode 9.0
  • 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 9.0 through locales.

Dependencies

  • Upstream release schedule.
  • If our patches does not come in upstream, we will try to patch it in Fedora. Though as per our upstream first policy we mostly avoid patching in Fedora.

Contingency Plan

  • Contingency mechanism: Will move change to Fedora 26 release.
  • Contingency deadline: Fedora 26 Beta release.
  • Blocks release? No
  • Blocks product? No

Documentation

Will provide it later.

Release Notes