Re: Admin: a suggestion on the script corruption problem.
Re: Admin: a suggestion on the script corruption problem.
- Subject: Re: Admin: a suggestion on the script corruption problem.
- From: Paul Berkowitz <email@hidden>
- Date: Sun, 18 Feb 2001 12:45:38 -0800
On 2/18/01 12:25 PM, "Chris Nebel" <email@hidden> wrote:
>
My point above was that there are only two places where I'd have to introduce
>
entirely new tokens for existing things, because the others already have
>
plain ASCII versions, even if the decompiler always munges them. This is
>
good, because altering the syntax of a language can be, shall we say,
>
disruptive, so you want to keep changes as small as possible.
Chris,
It's wonderful that you're going to all this trouble. And, as you say, there
are so few non-ASCII-7 characters in AppleScript that it might be a very
good idea to replace them. However, I'm sure that they will still crop up
both from people who don't know, or forget about, the switch you envision,
and in strings, but probably not too often.
It still seems rather a drastic solution for a mailing list problem
although, of course, you did mention much more important reasons for wanting
to make the change.
I'm still puzzled as to why this is an evidently easier solution than simply
reconfiguring the server's software. I can send any ASCII-8 character
whatsoever - any character typed using the option key on a Mac keyboard - to
the Microsoft newsgroup servers, and it comes back exactly as I typed it. I
tried with all our "problem" characters here - every one - and then some,
and back they all came, perfectly correct. I can also read the same
characters typed using different key combinations by other people on Windows
computers sent to the same newsgroups, and they all arrive on my Mac email
program (Entourage) exactly as they were sent and intended. Oh well.
--
Paul Berkowitz