Re: OT-ish warning: Apple is still using Mac Roman

2014-02-02 Thread Richmond
On 02/02/14 22:17, Bob Sneidar wrote: I recently was working on getting fields to accept unformatted text in a drag drop scenario. What I did was intercepted the drop, and then put the dropData [“text”] into the field. Something along these lines may be what you are looking for. As an aside,

Re: OT-ish warning: Apple is still using Mac Roman

2014-02-02 Thread Bob Sneidar
I recently was working on getting fields to accept unformatted text in a drag drop scenario. What I did was intercepted the drop, and then put the dropData [“text”] into the field. Something along these lines may be what you are looking for. As an aside, I was importing clipboard data from an

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Kay C Lan
On Fri, Jan 31, 2014 at 2:16 PM, Richmond wrote: > > Kay C Lan has, successfully, stated what I spent most of the night trying > to understand. > Whilst backward compatibility is great, there are always gotchas. And this doesn't just apply to commercials hardware/software etc, that seem to plan o

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Richmond
On 31/01/14 07:10, Kay C Lan wrote: Via the Apple Support forums. Pages is unicode. It can import, export and work with unicode no problem. An issue it does have, and seems to be right in line with your problem, someone was working with a Pages documents that was full of mathematical formuli an

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Kay C Lan
Via the Apple Support forums. Pages is unicode. It can import, export and work with unicode no problem. An issue it does have, and seems to be right in line with your problem, someone was working with a Pages documents that was full of mathematical formuli and these all came out mac roman; which

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Graham Samuel
Well, this horse is nearly dead, but perhaps a tiny bit more flogging might be of assistance. I have done a few more experiments, and strange as it may seem, they kind of work. If for example you use Pages to write a string containing some well-known Mac Roman 'specials', say pi, square root si

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Richmond
Things look pretty negative about Pages: http://en.wikipedia.org/wiki/Pages_%28word_processor%29 "As of November 2012, Pages does not support OpenDocument file format. The only known software other than Pages which can open its files is the Google Docs Viewer.[11] It can view the files, and sa

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Graham Samuel
Thanks Richmond, good observe as the Scots say (do you say it? RLS did.) In my case saving to .doc or any other format isn't on, because I can't predict what my users will do: if someone thinks a dash is a minus sign, then they will copy it regardless - I can't give them elaborate instructions t

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-30 Thread Graham Samuel
OK, you've convinced me that in my app I should allow any type of dash to stand in for a minus sign. It's not hard to do once you understand the need and in my case there is no requirement to use dashes for anything else. Thanks for the insight. Graham On 30 Jan 2014, at 08:36, Paul D. DeRocco

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-29 Thread Richmond
On 29/01/14 23:40, Graham Samuel wrote: I'm using LC 6.5.1 on a Mac with Mavericks. Recently I was given a Pages document with some text I needed to paste into a LiveCode desktop app. You can, save from Pages into Microsoft's ubiquitous .doc format. My younger son, who stays in Germany and us

RE: OT-ish warning: Apple is still using Mac Roman

2014-01-29 Thread Paul D. DeRocco
> From: Graham Samuel > > Ha! So the person who wrote the text just **thought** they > were minus signs. The trouble with the en dash (as opposed to > the em dash - I used to set type by hand, so I remember > these) is that the glyph in most fonts is very close to the > minus sign. I generall

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-29 Thread Graham Samuel
Thanks Devin Ha! So the person who wrote the text just **thought** they were minus signs. The trouble with the en dash (as opposed to the em dash - I used to set type by hand, so I remember these) is that the glyph in most fonts is very close to the minus sign. So maybe I haven't got a problem

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-29 Thread Devin Asay
On Jan 29, 2014, at 3:40 PM, Graham Samuel wrote: > More issues - the minus signs don't seem to be Mac Roman after all (at least > MacToISO no longer seems to translate the although I could have sworn it did > earlier, nor ASCII, nor anything else I've found so far. LC's charToNum > function t

Re: OT-ish warning: Apple is still using Mac Roman

2014-01-29 Thread Graham Samuel
More issues - the minus signs don't seem to be Mac Roman after all (at least MacToISO no longer seems to translate the although I could have sworn it did earlier, nor ASCII, nor anything else I've found so far. LC's charToNum function thinks their value is 208 (decimal). Still looking... Graham

OT-ish warning: Apple is still using Mac Roman

2014-01-29 Thread Graham Samuel
I'm using LC 6.5.1 on a Mac with Mavericks. Recently I was given a Pages document with some text I needed to paste into a LiveCode desktop app. The relevant text was: 3*(-1*x^2 + 4)(-1*x^4 - 5x + 2) (Don't worry, it's just a meaningless example). I changed this to plain text (it had originally