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

;use-livecode@lists.runrev.com> Cc: Kay C Lan <lan.kc.macm...@gmail.com> 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 <use-livecode@lists.runrev.com> wrote: > > However, the 'endpoints'

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

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

This is what I originally tested first (see my original post), but it didn't worked. The Umlaute (coming from a Mac client) entered the mySQL db corrupted. I don't know, if I could configure anything in my PHP or my db different to make this solution work. But since everything worked always fine

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

e-boun...@lists.runrev.com] Im Auftrag von Mark Waddingham via use-livecode Gesendet: Montag, 16. Januar 2017 17:42 An: How to use LiveCode <use-livecode@lists.runrev.com> Cc: Mark Waddingham <m...@livecode.com> Betreff: Re: AW: Why do I still need MacToISO, when working with UTF-8? Hi Tiemo,

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?

Im Auftrag von Mark Waddingham via use-livecode Gesendet: Montag, 16. Januar 2017 17:42 An: How to use LiveCode <use-livecode@lists.runrev.com> Cc: Mark Waddingham <m...@livecode.com> Betreff: Re: AW: Why do I still need MacToISO, when working with UTF-8? Hi Tiemo, Okay so, I'm assum

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

Hi Tiemo, Okay so, I'm assuming that all this code is running on the Mac client... *put fld "name" into myName* At this point myName contains a (text) string - thus encoding issues don't exist (you should think of text strings in memory as being stored in an 'encoding neutral' format).

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

Hi Mark, as a simplified pseudo code it looks like this: *put fld "name" into myName* -- ... *open file myFile for binary write* *write myName to file myFile* *close file myFile* -- ... *open file myFile for binary read* *read from file myFile until EOF* *close file myFile* *put it into myName*