Hi Bob,
Actually I think what I need to do is figure out what the original file
encoding is, and use that when I write out the export file.
I assume that the byte order mark (BOM) is for UTF-8
To see the BOM for UTF-8 make a button and a field named "fText"
Use this script for the button
Thanks Bernd. But I finally figured out what the issue was. It seems that
unless the output file is opened binary, any attempt to wrote to a file using
any of the cr, lf or crlf keywords in LC will result in LC auto-converting them
to cr, because that is the Macintosh standard. What I had to do
I also read up on the BOM, and for UTF-8 it is optional, and as mentioned not
recommended, because UTF-8 always uses the same byte order.
And anyway, the BOM was never the issue. Apparently Livecode always produces a
UTF-8 format file unless instructed to do otherwise.
Bob S
On Sep 17, 2024,
I went through all my code and replaced charToNum and numToChar with
codepointToNum and numToCodepoint respectively. If it matters to anyone, the
Quartum PDF, Excel and sqlYoga libraries all were using the depricated
versions.
Bob S
> On Sep 17, 2024, at 8:50 AM, Bob Sneidar via use-livecode
