Simon Montagu
smontagu@smontagu.org
Mozilla i18n development projects for 2016
Top priority bugs for Q1
ICU integration
Many of the bugs listed here depend to a greater or lesser
extent on integrating ICU API across all supported platforms.
The remaining blocker for this is
- Bug 1215247 Enable ECMAScript Internationalization API for Firefox on Android.
Moving this forward seems to depend chiefly on achieving size reduction to mitigate the increase in download size. At the same time, fixing it will enable a whole lot of clean up and removal of obsoleted code. The meta bug for that work (more dependencies need to be filed):
- Bug
1184116 Reduce i18n footprint where replaceable by ICU
We will also be able to move forward with using ICU implementation for a lot of i18n functionality, e.g.:
- Bug 728180 Update Unicode normalization
- BCP47 support (Bug 356038 and dependencies)
in particular, I'd like to fix Bug 556237, to make font preferences more sane & usable
RTL support
Lower priority issues for Q2-3
RTL support
- Bug 1169986 Text from attributes with dir="auto" should be displayed in the direction of the attribute, not the element
This has dependencies in Gaia:
- Bug 1134925 Log in page for Gmail when importing contacts shows Arabic placeholder text for username and password as left aligned
- Bug 1169648 The text in the title attribute is displayed in the wrong direction with RTL interface
- Bug 1173548 Reader View picks wrong direction for some RTL pages
IDN support and improvements to IDN display algorithm
- Bug 1226294 Distinguish between "URI not found" and "URI not accessed because invalid"
- Bug 993806 URL Bar text alignment in RTL mode
- Bug 1178095 Punycode doesn't handle interpuncts
- other bugs blocking bug 237820
Minor issues for Q4 or as time permits
RTL support
- Bug 1138419 Shift-Ctrl-Arrow moves in the wrong direction in an RTL textarea
- Bug 1198600 - The behaviour of the arrow keys in right-to-left languages is confusing
SMP support essential for emojis!
Generally speaking our SMP (supplementary character) support is good, but there are still a few issues remaining
- Bug 404856 Titles containing supplementary characters (outside BMP) are cropped in mid-surrogate-pair
- Bug 670837 maxlength shouldn't count one non-BMP character as two characters
- Bug 753262 Stop passing in lone surrogates to nsUnicodeProperties methods
- Bug 780449 Password fields display two replacement characters for a single supplementary Unicode symbol
- Bug 800856 XSLT/XPath string handling (e.g. string-length) should consider non BMP character as single character
- Bug 1100214 Selection Word by long tap sets incorrect range if range has non-bmp character such as emoji