Re: line breaking and indenting
Re: line breaking and indenting
- Subject: Re: line breaking and indenting
- From: Gakuji Ohtori <email@hidden>
- Date: Tue, 30 Jan 2001 02:19:49 +0900
>
Date: Sun, 28 Jan 2001 17:49:00 -0800
>
From: Paul Berkowitz <email@hidden>
>
>
On 1/28/01 12:34 PM, "Emmanuel" <email@hidden> wrote:
>
>
> At 17:39 +0100 28/01/01, Gakuji Ohtori wrote:
>
>> Question 1:
>
>>
>
>> The script
>
>>
>
>> set a to ,
>
>> {,
>
>> a:1,,
>
>> b:2,,
>
>> c:3,
>
>> }
>
> [snip]
>
>>
>
>> after a compilation. Are there any ways to avoid this? Probably not.
>
>>
>
>> Question 2:
>
>>
>
>> It seems records do not allow line-breaking with the continuation
>
>> character between their properties. No ways to line-break between
>
>> properties?
>
>
>
> You could insert the line-breaks *before* the commas:
>
>
>
> ------------
>
> set a to {a:1 ,
>
> , b:2 ,
>
> , c:3 ,
>
> } ,
>
> ------------
>
>
>
> This does not solve the residual first item problem "{a:1".
>
>
>
>
This whole thread has become incomprehensible, I think because the server is
>
changing line-breaks to yet more commas. I can't tell which comma is which.
>
>
Perhaps this thread could be moved over to MacScrpt which has a server that
>
respects Mac character formatting better than Apple's.
>
>
(BTW, I recently got a fancy complex HTML e-newsletter from Apple which had
>
similar mangled characters. And any files stored in an iDisk's Public Folder
>
at mac.com which use upper-ASCII characters in the file name appear to be
>
duplicated in the directory of its web-published version. You get two files
>
when there should be one: both distort the characters, but differently - one
>
of the them is the real file, the other is a phantom listing which errors
>
when you try to download. A real mess. So it seems that most of Apple's
>
servers are like this in mangling Mac-specific character mappings. Meanwhile
>
Microsoft's news and mail servers, of all things, display Mac formatting
>
without distortion. So Apple's distortions were not inevitable: they are a
>
result of some higher-level Apple person choosing Mac-hating servers for -
>
apparently - most of Apple's public servers.)
The first message <
email@hidden> distributed from
the list server has the following header:
>
X-MIME-Autoconverted: from quoted-printable to 8bit by lists.apple.com id f0SGck410475
I originally sent a message encoded to Quoted-Printable, but obviously
Apple's server converted the message to 8bit, which probably caused the
continuation characters to become commas. I have no idea why Apple's
list server is configured that way. It's clearly not the standard
behavior. Any message transfer agent should just transfer messages,
not convert them.
Gaji