add support for non-BMP ligatures
authorKonstantin Ritt <ritt.ks@gmail.com>
Thu, 26 Apr 2012 16:29:08 +0000 (19:29 +0300)
committerQt by Nokia <qt-info@nokia.com>
Fri, 4 May 2012 13:24:52 +0000 (15:24 +0200)
commit46b78113b22428e6f8540193fcf0e00591dbd724
treef7c0259844635c6a086e978d793deae16628a7bb
parent41b1fb918b7428aaebb2e237caa2f62a1667f0b1
add support for non-BMP ligatures

> http://www.unicode.org/versions/Unicode5.2.0/
D. Character Additions:
There are three new characters in the newly-encoded Kaithi script that will
require changes in implementations which make hard-coded assumptions about
composition during normalization. Most new characters added to the standard
with decompositions cannot be generated by the operations toNFC() or toNFKC),
but these three can. Implementers should check their code carefully
to ensure that it handles these three characters correctly.
U+1109A KAITHI LETTER DDDHA
U+1109C KAITHI LETTER RHA
U+110AB KAITHI LETTER VA

UCD 6.1 adds two more of them:
U+1112E CHAKMA VOWEL SIGN O
U+1112F CHAKMA VOWEL SIGN AU

Change-Id: I781a26848078d8b83a182b0fd4e681be2a6d9a27
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
src/corelib/tools/qchar.cpp
src/corelib/tools/qunicodetables.cpp
tests/auto/corelib/tools/qchar/tst_qchar.cpp
util/unicode/main.cpp