AW: AW: AW: Why do I still need MacToISO, when working with UTF-8?

C Lan Betreff: Re: AW: AW: Why do I still need MacToISO, when working with UTF-8? On Tue, Jan 17, 2017 at 1:24 AM, Mark Waddingham via use-livecode wrote: > > However, the 'endpoints' (i.e. where the developer can 'see' encoded > text output - e.g. when writing to a f

Re: AW: AW: Why do I still need MacToISO, when working with UTF-8?

On Tue, Jan 17, 2017 at 1:24 AM, Mark Waddingham via use-livecode wrote: > > However, the 'endpoints' (i.e. where the developer can 'see' encoded text > output - e.g. when writing to a file, or encoding for a URL) had to remain > as before otherwise all existing applications using anything other t

Re: AW: AW: Why do I still need MacToISO, when working with UTF-8?

Hi Tiemo, As an additional note (if you don't absolutely need to write binary) it is also possible to use the syntax /open file for "utf8" text read/ or /open file for "utf8" text write/ in which cases the engine takes care of encoding/decoding the string using UTF-8 encoding. Then, w

Re: AW: AW: Why do I still need MacToISO, when working with UTF-8?

Hi Tiemo, thank you for taking your time and clarifying. I wasn't aware that the internal format on a Mac client is MacRoman. I thought it would be a "neutral" UTF-8 format. Internally, the engine uses either MacRoman/ISO-Latin1 *or* UTF-16 depending on platform and what the string contains.

AW: AW: Why do I still need MacToISO, when working with UTF-8?

Hi Mark, thank you for taking your time and clarifying. I wasn't aware that the internal format on a Mac client is MacRoman. I thought it would be a "neutral" UTF-8 format. Thanks Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag v