Hi Slava,
This can happen when a website uses (binary) unicode text instead of html
encoded text. Externals can't pass binary data to the LiveCode engine. As a
result, LC gets incorrectly encoded text and text that cannot be decoded is
replaced with question marks.
Sockets, however, can pass
Another option you could try is something like the following
*-- uses javascript to place the body of the current page into the tText
variable.*
*put revBrowserExecuteScript(sBrowserId,result=document.body.innerHTML)
into tText*
and see if javascript sets the result correctly so you can use
property for Unicode text
Nevermind, just tried it, doesn't work correctly. innerText doesn't work
either.
On Fri, Jun 3, 2011 at 6:36 AM, Mike Bonner bonnm...@gmail.com wrote:
Another option you could try is something like the following
*-- uses javascript to place the body of the current
When my revBrowser instance displays a UTF-8 Web page, and I look at the
value returned by revBrowserGet(instanceID htmltext), I think all
double-byte characters are replaced with question marks. I think the same is
true of the revBrowser selected property.
Could someone please confirm? I don't
