summaryrefslogtreecommitdiffstats
path: root/mkspecs
diff options
context:
space:
mode:
authorSimon Hausmann <simon.hausmann@nokia.com>2011-05-16 14:04:31 +0200
committerSimon Hausmann <simon.hausmann@nokia.com>2011-05-20 13:55:12 +0200
commit4f2138ecfbdc58e5cb5b0c7d762197ef69752957 (patch)
tree71625f3ececa3b5b4b9a49bc71a11d6d9a79693e /mkspecs
parent80d094f07272663d759ec4bd8e8a8c233753dd46 (diff)
Fix inconsistency between Qt and ICU in Shift-JIS codec with regards to ASCII range
Qt's Shift-JIS codec maps the characters 0x5c and 0x7e to unicode yen (0x5a) and unicode overline (0x203e). ICU and (as it turns out) Symbian's native Shift-JIS codec preserve 0x5c and 0x7e when converting to Unicode. Qt's behaviour creates a problem when loading japanese web sites that are encoded in Shift-JIS. When they reference external JavaScript files, those tend to inherit the current page encoding (unless the character set is explicitly specified). Consequently JavaScript tends to contain regular expressions (as a built-in feature of the language), which in turn uses backslashes for escape sequences. Therefore it is crucial that the encodings used to decode the script preserve the ASCII range, i.e. do not convert 0x5c (ascii backslash) to something else. This patch corrects the behaviour of Qt's Shift-JIS codec to leave all characters < 0x80 unaltered in the process of conversion to and from Unicode. Task: QTBUG-19335 Reviewed-by: Lars Knoll <lars.knoll@nokia.com> (cherry picked from commit 8e321cd869da7ff1cf0168da41aa0246b44867cc)
Diffstat (limited to 'mkspecs')
0 files changed, 0 insertions, 0 deletions