Re: path to as string
Re: path to as string
- Subject: Re: path to as string
- From: Shane Stanley <email@hidden>
- Date: Wed, 29 Jun 2005 11:45:50 +1000
- Thread-topic: path to as string
On 29/6/05 10:11 AM, "has" <email@hidden> wrote:
> Have you any specific examples?
As you suggest, there are lots of older apps -- and old code. Importantly,
there are issues once you start using read/write with strings -- if you have
a string that has styling and you write it to a text file, you strip off the
styling. (Who is writing all their text out as Unicode files? Deliberately,
I mean ;-))
I agree in principle with the idea that implementation of such things should
normally be hidden, but in this case you need some explanation of, for
example, why what you get when you read a file *might* be different from
what you wrote -- indeed, it might be different depending on *where* you
read and write it.
An explanation of the mechanism is a much better answer than just "because"
-- users need to know that strings are potentially fragile things, and if
you're going to tell them that, you might as well tell them why so they can
have some idea of where they're likely to get bitten. (As a bonus, they
might appreciate why the move to Unicode is a good thing.)
If the whole implementation wasn't such a kludge, we could all be blissfully
ignorant. And maybe we wouldn't be looking so longingly towards the day when
it's just a bad memory.
As a poor typist, I just wish typing "as Unicode text" could be shortened...
(And I think the Finder bug is now fixed.)
--
Shane Stanley <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden