Problem with Latin 1 (I think)

[Ken Corey]

I expect you're running up against UTF8 characters in your html (just 
like the thread "Japanese characters in HTML result").  What's the 
encoding of the page?

Here's what I wrote in that thread.  Try it and see if it solves the 
problem:

On 04/02/2012 05:14, Bob Sneidar wrote:
 > So the trick is to programmatically determine what is double byte and 
what is not?

Well, if you take a look at the headers from that page, the 
Content-Type: "text/html; charset=UTF-8"

Which is specifies exactly how the data will fall:
http://en.wikipedia.org/wiki/UTF-8

For regular ascii characters, nothing changes. For the higher ranges, 
you could have 2 to 4 bytes per character.

http://runrev.com/newsletter/december/issue62/newsletter2.php

I've not tried it, but I think your solution is something like this:

    put "https://www.googleapis.com/books/ETC"  into tURL
    get url tURL
    set the unicodeText of field X to uniencode(it,"UTF8")

As I understand it, you've got to get the text from UTF8 into the 
internal representation of a string.  Then, for the field to understand 
it and display it properly, you must put the string into the unicodeText 
of it.

Hope that helps.

-Ken

On 06/02/2012 09:43, Geoff Canyon Rev wrote:
> I'm retrieving a url and parsing the HTML. If I view the URL in Safari (all
> of this on a mac) there are places where safari shows "isn’t" but livecode
> shows "isn’t"
>
> I'm using 5.0.2, and isotomac doesn't seem to fix this. Any suggestions?