New issue
Advanced search Search tips

Issue 602128 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocking:
issue v8:4477



Sign in to add a comment

Lithuanian lower/uppercasing: should use transliterator

Project Member Reported by js...@chromium.org, Apr 10 2016

Issue description

For Blink's css-transform, Greek uppercasing was made to use transliterator instead of regular case conversion API in ICU. 

When working on that, I made a test to see if any other languages requiring special treatment for case conversion also need to rely on transliterator. I did test for Lithuanian, but my test was not comprehensive enough to catch cases where the current ICU's case conversion API (for Lithuanian locale) is not sufficient. 

Lithuanian does need to reply on transliterator (until ICU's case conversion API support it behind the scene). 

This requires adding lt-Upper and lt-Lower rules to Chrome's copy of ICU data (they're dropped because nobody uses it to save the space even though they're tiny). 

This will help v8's toLocale{Upper,Lower}Case("lt") (v8: bug 4476 )
 

Comment 1 by js...@chromium.org, Apr 10 2016

It's  bug v8:4476 

Comment 2 by js...@chromium.org, Apr 10 2016

Blocking: -v8:4476 v8:4477
Actually, it should be  bug v8:4477 

Comment 3 by js...@chromium.org, Apr 11 2016

Status: WontFix (was: Assigned)
I was misled by a difference in canonicalization (NFC vs non-NFC) between case conversion API and transliteration API. Lithuanian is fine with case-conversion API. 

See http://bugs.icu-project.org/trac/ticket/10582, http://unicode.org/cldr/trac/ticket/6921 and http://unicode.org/cldr/trac/ticket/7039

Sign in to add a comment