[Info-vax] Open Source on OpenVMS - A Progress Report

[David Biddulph]

"Richard B. Gilbert" <rgilbert88 at comcast.net> wrote in message 
news:G86dnWQgCeAv4kHXnZ2dnUVZ_hOdnZ2d at giganews.com...
> Phillip Helbig---remove CLOTHES to reply wrote:
>> In article
>> <f5b6cb43-4328-4b26-b5d8-fd662df8cbde at m11g2000yqf.googlegroups.com>,
>> BillPedersen <pedersen at ccsscorp.com> writes:
>>> On Oct 19, 3:08=A0am, hel... at astro.multiCLOTHESvax.de (Phillip Helbig---
>>> remove CLOTHES to reply) wrote:
>>
>> Bill's full reply is below.
>>
>> Let me kindly suggest, not just with respect to VMS freeware activities, 
>> the following:
>>
>>    o  Don't quote too much text
>>
>>    o  Don't post quoted-printable stuff to a text-based newsgroup like 
>> comp.os.vms
>>
>> Discussion is good, but it needs to be easy so that no time is wasted. 
>> The points above make it easier and, of course, apply to all newsgroup 
>> posts.  Also, though you didn't do so:
>>
>>    o  Don't top-post
>>
>> is also an essential rule.
>>
>> With regard to the quoted-printable stuff: it might be that you always 
>> see the text "correctly" because of some software conversion.  But other 
>> folks might not.
>>
>> Note that there is also no need to encode anything I wrote, since I used
>> only 7-bit printable US-ASCII.  Why encode a space as "=A0", for
>> example?
>
> The second of two consecutive space characters will be encoded as "=A0".
> I have no idea why or even which mailers exhibit this behavior.  For 
> example I just typed two consecutive spaces following a period because 
> that's the way I learned to type English text.  For some mail programs 
> this will be a problem, for others, not!

hex A0 is, of course, a non-breaking space, as distinct from hex 20, which 
is an ordinary space.
-- 
David Biddulph