Re: bfobserver daemon
Re: bfobserver daemon
- Subject: Re: bfobserver daemon
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 31 May 2006 11:24:26 -0700
- Thread-topic: bfobserver daemon
On 5/31/06 9:40 AM, "Jonas Maebe" <email@hidden> wrote:
> There was no space in your original post, at least not one which got
> put there by Copy/Paste. Mail however breaks all lines at 70
> characters, and where it breaks them it adds a space. The relevant
> line was split like this:
>
> sudo launchctl unload -w /System/Library/LaunchDaemons/[SPACE]
> com.apple.dnbobserver.plist
>
>
> However, it also adds "delsp=yes; format=flowed" to the content-type
> header, which instructs mail clients that open this message to kill
> those superfluous newlines and spaces. Apart from Mail.app, most mail
> clients don't support this though (which is annoying if you post long
> url's on a list and all non-Mac users complain your mail client is
> broken; rdar://problem/4146263 is marked as a duplicate).
Although Entourage does not write format=flowed, it does read it correctly.
Eudora can both read and write it (with suitable option selected for
writing/sending, I believe). Normally, any message sent format=flowed
appears in Entourage with its long lines restored. However, Bill B's message
did NOT appear this way in Entourage: lines were broken. (I believe that the
RTF protocol requires lines to break, at the outside, at the nearest
word-end to 80 characters, or 79 for format=flowed so the space can be
added. Sending clients often break at an earlier column for reason to do
with including > characters, etc.)
I do not understand why it displayed for you (Jonas) in Mail with long
lines, but not so in Entourage, unless - unknown to me the latest version of
Entourage (11.2.3) has broken format=flowed read support or it simply
doesn't understand "delsp=yes" which I've never seen before: format-flowed
support on its own should delete the spaces.
[I would have guessed that it was the mailing list server that doesn't
support or respect format=flowed and just transmits the source as sent with
breaks and spaces added. The combination of a sending client (Mail) that
doesn't allow you to turn off format=flowed (?) and a list server that
doesn't respect is indeed a recipe for disaster when transmitting code where
such things matter. But if recipients with Mail saw long lines, this does
not apply here.]
Better to send in HTML, if the list server supports it (I believe it does),
in that case. Except maybe Mail can't compose HTML?
--
Paul Berkowitz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden