Bug 58967 - [Qt] Some Unicode Characters are not displayed
Summary: [Qt] Some Unicode Characters are not displayed
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks: 55056
  Show dependency tree / graph
 
Reported: 2011-04-19 23:48 PDT by Rakesh Sadhu
Modified: 2014-02-03 03:17 PST (History)
4 users (show)

See Also:

Attachments
QtTestBrowser SisX file (34.23 KB, application/octet-stream)
2011-04-19 23:48 PDT, Rakesh Sadhu 		no flags Details
html file (22.97 KB, text/html)
2011-04-19 23:49 PDT, Rakesh Sadhu 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rakesh Sadhu 2011-04-19 23:48:39 PDT 
Created attachment 90315 [details]
QtTestBrowser SisX file

Precondition:
----------------
1.  Flash the hardware with Sr11.1 build Wk10
2. Install the attached sisx Files
3.  Reboot the device

Steps to Reproduce:
Launch the html Page containing Utf Characters, using qttestbrowser app

Expected Result:
All Characters should be rendered properly.

Actual Result:

Few characters are not rendered viz special mathematical characters , carriage
return etc.
Comment 1 Rakesh Sadhu 2011-04-19 23:49:04 PDT 
Created attachment 90316 [details]
html file
Comment 2 Janne Koskinen 2011-04-20 07:03:12 PDT 
Hmm... I remember a talk about disabling kerning and shaping https://lists.webkit.org/pipermail/webkit-qt/2009-December/000047.html ; Was this done?
Comment 3 Laszlo Gombos 2011-05-24 16:08:14 PDT 
There is some related discussion in bug 60786.
Comment 4 Jocelyn Turcotte 2014-02-03 03:17:34 PST 
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.