Re: Chevrons again (Re: compiler directive, was (Follow-up on
Re: Chevrons again (Re: compiler directive, was (Follow-up on
- Subject: Re: Chevrons again (Re: compiler directive, was (Follow-up on
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 24 Jan 2001 08:18:59 -0800
On 1/24/01 7:27 AM, "Arthur J Knapp" <email@hidden> wrote:
>
> Date: Wed, 24 Jan 2001 11:20:35 +0100
>
> From: "Serge Belleudy-d'Espinose" <email@hidden>
>
> Subject: Chevrons again (Re: compiler directive, was (Follow-up on
>
> appletalk volume mounting))
>
>
> At 11:56 -0500 19/01/01, Arthur J Knapp wrote:
>
>
>
>> P.S. The characters preceeding and following "event sysodlog"
>
>> are option-backslash and shift-option-backslash,
>
>> respectively. (Take that, mail server).
>
>
> Being one of the many non-english born on this list, I feel concerned
>
> everytime I read this. Why not just use << and >> for displaying chevrons
>
> on the list, and assume not everyone can access them by option-backslash and
>
shift-option-backslash?
>
>
>
> Sorry, just my morning rant.
>
>
Don't be :)
>
>
I am not insensitive to the concerns of AppleScripter's from around
>
the world, (unless their names are Nigel Garvey or Shane Stanley).
>
>
Is there some reason that 21st century mail-servers must act in this
>
way? I mean, why not just create a new Internet protocal called, "FTP-Mail",
>
where 8-bit messages are passed back and forth?
Just out of interest: the Microsoft news servers (which may be a very
different matter, of course), plus the mail servers used by MS's Outlook
Express and Entourage mailing lists, transcribe Macintosh character
formatting perfectly, including all upper-ASCII characters thrown at them,
whereas Apple's mangles them in the was we see every day. Odd, isn't it?
--
Paul Berkowitz