Thanks Ben, that’s really interesting. It never occurred to me that these html
files might be anything other than simple plain text files, as I’d work with in
Coda, etc., for years.
The local HTML files are storage of the HTML text pulled from the LiveCode
browser widget, saved using the URL ‘
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #265 here: https://bit.ly/3u2Upex
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
Thanks for getting back to me on this.
This bug has been around for over 3 years now.
Will it ever get squashed?
Rick
> On May 15, 2021, at 12:06 PM, matthias rebbe via use-livecode
> wrote:
>
> There is a bug report for this already
>
> https://quality.livecode.com/show_bug.cgi?id=21233
>
>
Hi Keith,
The thing with character encoding is that you always need to know where it's
coming from and where it's going.
Do you know how the HTML documents were obtained? Saved from a browser,
fetched by curl, fetched by Livecode? Or generated on disk by something else?
If it was saved from
Hi folks,
I’m using LiveCode to summarise text from HTML documents into csv summary files
and am noticing that when I extract strings from html documents stored on disk
- rather than visiting the sites via the browser widget & grabbing the HTML
text - weird characters being inserted in place of
