{ "id": "61250", "key": "TIMOB-618", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11223", "name": "Release 1.3.0", "archived": true, "released": true, "releaseDate": "2010-05-05" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:53:42.000+0000", "created": "2011-04-15T02:33:03.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "defect" ], "versions": [], "issuelinks": [], "assignee": { "name": "mculpepper", "key": "mculpepper", "displayName": "Marshall Culpepper", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:53:42.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
Might be as simple as adding content type the binding.
(from [f679c2b927cd80738069c4a11c766d84d941cee1])\nadding a content type meta tag to the unicode example seems to at\nleast fix the display of characters in android WebView. re-enabled\nlogging/unicode test [#618] \nhttp://github.com/appcelerator/titanium_mobile/commit/f679c2b927cd8...
utf-8 strings in a label is displayed as the little boxes :)
\nfor example this string...\nயாமறிந்த having\nbeen returned from deserialised (eval) on some json via an\ncreateHTTPClient, shows as boxes in Android - it's ok in\niPhone.
Cant tell if its in the eval or the label for now - but thought\nyoud like to know
Thanks for the info Dan.
\nOne of the weird things I've seen while testing is that certain\nUnicode characters just don't seem to decode at all (showing the\n\"empty box\" instead). From the iPhone example, about 25% of the\ncharacters show up, but the rest show as boxes. I'm not sure if\nthis is a limitation in Android, or maybe just a limitation in\nAndroid's implementation of UTF-8
Just confirmed the console logs work as long as you have a UTF-8\nConsole. Eclipse LogCat is the devil.. resolving.