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: [OT] Website Design Apps-Mac

On Mon, Oct 17, 2016 at 6:53 AM, Matthias Rebbe < matthias_livecode_150...@m-r-d.de> wrote: > One problem i see with WordPress is, that its popularity make it a popular > target for hackers. ... and I was a target of Indonesian Script Kiddies several sites, but their autoupdates are VERY

Re: Another naive question about code signing

Thanks Matthias. Sadly I didn’t really understand Trevor’s explanation as I got lost understanding what the ‘tool’ was - maybe it was Ksign. But AFAIKS, making the installer and then signing it doesn’t produce a different result from making the installer maker (Innosetup) do the signing. But as

Re: Documentation on Dispatch

Right. A property set is an array of properties if I am not mistaken. So portal_RowNames is the "array" name and headerName is a variable which holds a value resolving to the name of the property. Hence it compiles. Bob S On Jan 16, 2017, at 10:45 , Jeanne A. E. DeVoto via use-livecode

Re: Documentation on Dispatch

At 6:56 PM + 1/13/2017, Sannyasin Brahmanathaswami via use-livecode wrote: But I found this in a script from an associate: setprop portal_RowNames [headerName] rowNames and it compilesŠ the first param is a variable inside square braces. Not sure it this is some LC magic or just this

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,

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

Mark, thanks again for your explanations. That explains some strange things here in the past… ;) Matthias Matthias Rebbe Bramkampsieke 13 32312 Lübbecke Tel +49 5741 31 +49 160 5504462 Fax: +49 5741 310002 eMail: matth...@m-r-d.de BR5 Konverter - BR5

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

Am 16.01.2017 um 18:30 schrieb Mark Waddingham via use-livecode >: Sure - here is how I'd slightly adjust Tiemo's code: *put fld "name" into myName* -- ... *open file myFile for binary write* *write textEncode(myName,

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

Hi Mark, thanks for that. > Am 16.01.2017 um 18:30 schrieb Mark Waddingham via use-livecode > >: > > > Sure - here is how I'd slightly adjust Tiemo's code: > > *put fld "name" into myName* > -- ... > *open file myFile for

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

Hi Matthias, On 2017-01-16 18:25, Matthias Rebbe via use-livecode wrote: It would have been nice if you had also put some sample code for how to UTF8 encode the string. That would have made your explanations complete. ;) Sure - here is how I'd slightly adjust Tiemo's code: *put fld "name"

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

Hi Mark, although i am not the original poster i really appreciate you explanation. The only thing what was missing … It would have been nice if you had also put some sample code for how to UTF8 encode the string. That would have made your explanations complete. ;) I am pretty sure there are

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

Re: Tarting up the scriptEditor

Yes I get notified on each post. - Andy Piddock My software never has bugs. It just develops random features. TinyIDE a Free alternative minimalist IDE Plugin for LiveCode TinyIDE Script editor Themer for LC http://2108.co.uk PointandSee is a FREE simple but full featured under

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*

Re: [OT] KOUSEK (or replacement) code snippet manager replacement?

I can think of an application for an XML to Array handler. Toshiba copiers backup their address books and "template" registrations as xml now, but other copiers are not capable of interpreting or importing them. It might be possible to create a conversion tool if I can parse the XML properly.

RE: [OT] KOUSEK (or replacement) code snippet manager replacement?

Hi Stephen, I have bought {source} in the past and I understand it is now open source and available at GitHub. You can take a look at http://www.getsourceapp.com/ Goodluck, Erik Beugelaar -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of

Re: Tarting up the scriptEditor

Hi Andy, yes the email arrived here 2 minutes after i sent my post to the list. I saw there is a forum now on your site. Are you informed automatically if someone posts something to the Seth Bug Reports forum? If not, please have a look. ;) Regards, Matthias > Am 16.01.2017 um 13:45

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

Hi Tiemo, On 2017-01-16 11:57, Tiemo Hollmann TB via use-livecode wrote: Now my German Umlaute don't get corrupted in the MySQL db and everything is fine, but I would like to understand the technical background. Why do I still need MacToISO() in LC 8 on a Mac and even worse, I didn't needed

Re: Tarting up the scriptEditor

Hi Matthias, Have you received the email re the update? It has a link and instructions on how to install the latest version. The auto updated can be flakey so I've reverted to a manual install method. - Andy Piddock My software never has bugs. It just develops random features.

[ANN] This Week in LiveCode 66

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 #66 here: https://goo.gl/0WKu5k This is a weekly newsletter about LiveCode, focussing on what's been going on in and around

Re: Tarting up the scriptEditor

Hi Andy, first of all thanks. Unfortunately the update check in revSeth 2.1 still tells me that i have the latest version. Regards, Matthias > Am 16.01.2017 um 12:59 schrieb AndyP via use-livecode > >: > > A new version

Re: Tarting up the scriptEditor

A new version (2.2) of Script Editor Themer has been released. Release notes can be viewed here. http://2108.co.uk/script-editor-themer/script-editor-themer-release-notes/ Now works with* Community* and *Commercial* versions of LiveCode This fixes the problems with V8 onwards. - Andy

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

Hello, Probably my knowledge about code sets is too limited. My thinking was, that UTF-8 includes the same characters above ASCII 128 independent of the platform and makes data transfer between different platform compatible without conversion of a char set. Migrating a LC 6 program to LC 8 I just

AW: Another naive question about code signing

Hi Graham, as I understand you, you are concerned, why there are still warnings, though you have signed your installer. That is standard since Win 7. The "only" difference is, that the warnings show the text "... of the trusted developer xy" instead of "... of unknown developer". But you can't