best/fastest way to tell if a field contains unicode text?

[Bob Sneidar]

<sigh> Apple vs Microsoft anyone? I’m not a huge Microsoft fan, but I have to work with it everyday as part of my job, so I’ve learned to live with it. But Apple of late has not blown my skirt up either. Soldering memory to the motherboard?? And why??? Well they will cite cost of production, but how curious that we can no longer take advantage of the price match guarantee on a memory upgrade when we walk into a store and buy a laptop instead of paying three to four times the market price for Apple memory. And glueing the battery to the case… well seems we have to take it to Apple to get serviced if the battery needs replacing now, don’t we? 

Bob


On Mar 21, 2014, at 07:08 , Geoff Canyon <gcanyon at gmail.com> wrote:

> On Fri, Mar 21, 2014 at 6:56 AM, Fraser Gordon <fraser.gordon at runrev.com>wrote:
> 
>> That's the reason behind most of the functions we've marked as deprecated
>> in 7.0 - upgrading them to support Unicode would break existing stacks in
>> subtle ways (e.g. numToChar - somebody, somewhere, might be depending on
>> the fact that it interprets the number modulo 256. Plus, it takes the
>> native encoding rather than Unicode codepoints).
> 
> 
> <blunt>That's the Microsoft way to handle this. The Apple way would simply
> be to do the right thing -- if you want to be nice, issue a note that
> backwards compatibility is being broken and specify how and the
> reasons.</blunt>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode