[Webkit-unassigned] [Bug 32416] New: [Qt] CWRT fails to detect the character encoding through BOM detection for UTF-8 for text/html docs

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=32416

           Summary: [Qt] CWRT fails to detect the character encoding
                    through BOM detection for UTF-8 for text/html docs
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: S60 Hardware
        OS/Version: S60 3rd edition
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P3
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: peojala11 at gmail.com


When the content type is text/html and the encoding not specified through any
of the http header or xml encoding or meta tag methods, then UA must look at
the BOM and find out if it is UTF-8 and display the contents accordingly. In
this test case, the test file is saved in utf-8 encoding. 

Steps to reproduce:

1. Load:
http://waplabdc.nokia-boston.com/browser/users/charset/Charset_detection/index.asp
2. Select Hindi as phone language and either utf-8 or ISCII as encoding from
select lists and
then click the "Test Link".
3. An index page with a list of tests is loaded. 

4. Click the link:
nocharset_xhtml_text_html




Expected Result: A page will be loaded which shows text "nokia" in hindi
language font.

Actual result: Unidentified characters are displayed instead of hindi font.


Note that if the content type is application/xhtml+xml or application/xml or
text/xml then CWRT correctly identifies charset encoding in such cases if the
document served is originally saved as a utf-8 document.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.