Re: When a string is not a string for Palm Desktop
Re: When a string is not a string for Palm Desktop
- Subject: Re: When a string is not a string for Palm Desktop
- From: Richard Morton <email@hidden>
- Date: Fri, 2 May 2003 21:07:18 +1000
On Friday, May 2, 2003, at 07:41 PM, Chris Page wrote:
On Thursday, May 1, 2003, at 21:22 US/Pacific, Richard Morton wrote:
The variable newCCLPathStr should be a plain old string, though it
seems to contain one of these new string classes that look like
Unicode and resist all normal attempts at coercion to plain text.
It's either a 'string' or 'international text'.
Must be 'international text' then I guess. ;) Somewhere along the
line the string - a full path - was made up using some Unicode perhaps.
I coerce it to string in the script & under OS 8/9 it was always plain
text, but under X it's styled.
Palm Desktop 4.1 returns international text if the current application
script code is not MacRoman, to preserve the correct interpretation of
the characters. Otherwise, it returns a plain string, where you are to
assume it's MacRoman (which seems to be what most people do by
default). In fact, I was going to just return international text all
the time, except that people complain about it, as you did.
I wasn't actually meaning it as a complaint about the new PD which, as
noted elsewhere, I think is fantastic. There may be some confusion
here too - I'm not getting the string from PD, I'm trying to feed it to
PD.
Insofar as I was complaining, it was more that I couldn't remove the
style from the string without a hack & the fact that AS is opaque about
the class - if it's international text, then it would be handy if AS
would tell me so.
What language is Palm Desktop displaying in the UI?
English.
PD 4.1 baulks at setting one of its text fields to this, though older
versions dealt with it OK. The script returns the error "Can't make
<<script>> into a string"
Unfortunately, it looks like you found a bug here. When you set the
title of a memo Palm Desktop tries to coerce the value to a Pascal
string ('pstr'), which fails. Coercing to text ('TEXT') seems to work,
though.
Looks like we might be talking about two different things - I'm trying
to set the field text of a custom field of an address.
So Palm Desktop may just not be handling international text properly
for fields that are limited to 255 characters.
You may be right there. As mentioned, PD4.0 did accept this text.
Can you set the memo contents to this text value?
Just tested it and - yes, it works fine. The same string that errors
going into the field text of a custom field of an address is accepted
by the memo contents.
Thanks for the reply and thanks again for all the work on PD4.1 - as
far as I'm concerned the scripting has gone from ugly to excellent. If
this & the 'contents of contents' issue are your only 2 bugs, I'd say
you're well in front of the pack! I hear the Cocoa team could use a
hand if you're looking for work... ;-)
Cheers,
String Bean
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.