[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 301610] New: Please include upstream patch for bidi-mirroring update in qt-copy
From:       Shai <shai () platonix ! com>
Date:       2012-06-10 22:12:08
Message-ID: bug-301610-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=301610

            Bug ID: 301610
          Severity: wishlist
               URL: https://bugreports.qt-project.org/browse/QTBUG-25169
           Version: unspecified
          Priority: NOR
          Assignee: unassigned-bugs@kde.org
           Summary: Please include upstream patch for bidi-mirroring
                    update in qt-copy
    Classification: Unclassified
                OS: Linux
          Reporter: shai@platonix.com
          Hardware: Debian unstable
            Status: UNCONFIRMED
         Component: general
           Product: kde

(copied from the Qt bug linked as URL)

Unicode 6 changed the bidi-mirroring properties of some characters (see
http://unicode.org/versions/corrigendum6.html). Of these characters, the
characters 2019,201A (single quotes), 201D and 201E (double quotes) are used in
Hebrew (and are to be included in a soon-to-be-released new Hebrew Keyboard
Layout standard).

Qt still uses the old definitions. The result is a regression-by-default: If I
wrote this comment in an RTL language (like Hebrew), using the proper Hebrew
quotes (open with U201E and close with U201D), it would be presented
incorrectly in any Qt-based browser.


Reproducible: Always

Steps to Reproduce:
In any KDE app which supports this,
1. Turn on BiDi support in qtconfig
2. Write RTL text containing fancy quotes like U+201D

Actual Results:  
The character U+201D is mirrored (Unicode 5.0 behavior)

Expected Results:  
The character U+201D is not mirrored (Unicode corrigendum 6 and later behavior)

Qt has included this patch in their master, and it will be released with 5.0.
KDE can do so sooner.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]