Closed Bug 606917 Opened 9 years ago Closed 9 years ago
Update data files to Unicode 6
The patch was prepared by the procedure described at https://wiki.mozilla.org/I18n:Updating_Unicode_version. (gfx/thebes/src/ignorable.x-ccmap isn't included in the patch because there were no changes to it)
Attachment #485686 - Flags: review?(VYV03354)
Attachment #485686 - Flags: review?(VYV03354) → review+
Comment on attachment 485686 [details] [diff] [review] Patch Asking approval2.0 in order to maintain our policy that releases always support the latest version of Unicode. There are no code changes in the patch, only script-generated data tables and tests.
Attachment #485686 - Flags: approval2.0?
This similarly updates the data tables used by the harfbuzz font back-end so that new scripts and characters in Unicode 6.0 will be handled appropriately (subject to font support, of course). No actual code changes; just added new script constants to the harfbuzz header, and regenerated the lookup tables using the tool at gfx/thebes/genUnicodeScriptData.pl based on the UCD 6.0.0 data files.
Attachment #487236 - Flags: review?(smontagu)
Attachment #487236 - Flags: review?(smontagu) → review+
http://hg.mozilla.org/mozilla-central/rev/8cbe83542596 (first patch)
Assigning to Jonathan for patch 2
Assignee: smontagu → jfkthame
Comment on attachment 487236 [details] [diff] [review] patch 2: update character property tables for harfbuzz to unicode 6.0 We should take this for 2.0 as part of ensuring that we support the current Unicode version. (The additional scripts aren't all that important as we don't have any specific behavior for them yet, but this will also ensure we have the correct behavior for new characters that have been assigned to existing scripts that we do process such as Arabic.)
Attachment #487236 - Flags: approval2.0?
First patch was backed out and relanded in http://hg.mozilla.org/mozilla-central/rev/51f3baa68656
Pushed patch 2: http://hg.mozilla.org/mozilla-central/rev/1b2bdf54fe82
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.