Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-618] Android: HTML WebView with Unicode Fails

GitHub Issuen/a
TypeBug
PriorityMedium
StatusClosed
ResolutionFixed
Resolution Date2011-04-17T01:53:42.000+0000
Affected Version/sn/a
Fix Version/sRelease 1.3.0
ComponentsAndroid
Labelsandroid, defect
ReporterDon Thorp
AssigneeMarshall Culpepper
Created2011-04-15T02:33:03.000+0000
Updated2011-04-17T01:53:42.000+0000

Description

Might be as simple as adding content type the binding.

Comments

  1. Marshall Culpepper 2011-04-15

    (from [f679c2b927cd80738069c4a11c766d84d941cee1]) adding a content type meta tag to the unicode example seems to at least fix the display of characters in android WebView. re-enabled logging/unicode test [#618] http://github.com/appcelerator/titanium_mobile/commit/f679c2b927cd80738069c4a11c766d84d941cee1"> http://github.com/appcelerator/titanium_mobile/commit/f679c2b927cd8...

  2. Dan Mullineux 2011-04-15

    utf-8 strings in a label is displayed as the little boxes :)

    for example this string... யாமறிந்த having been returned from deserialised (eval) on some json via an createHTTPClient, shows as boxes in Android - it's ok in iPhone.

    Cant tell if its in the eval or the label for now - but thought youd like to know

  3. Marshall Culpepper 2011-04-15

    Thanks for the info Dan.

    One of the weird things I've seen while testing is that certain Unicode characters just don't seem to decode at all (showing the "empty box" instead). From the iPhone example, about 25% of the characters show up, but the rest show as boxes. I'm not sure if this is a limitation in Android, or maybe just a limitation in Android's implementation of UTF-8

  4. Marshall Culpepper 2011-04-15

    Just confirmed the console logs work as long as you have a UTF-8 Console. Eclipse LogCat is the devil.. resolving.

JSON Source