news.software.readers

me@ wrote:
> Whiskers wrote in
> news: @ t:
>
>> On 2007-08-07, bealoid wrote:
>>> »Q« wrote in
>>> »news: @ :
>>>
>>>> In , "-Lost"
>>>> wrote:
>>>>
>>>>>I realize this is rather vague... actually just pointless. But I
>>>>>find it odd that I see so many threads where the first post is
>>>>>"Re:". For example, Charles Lasitter's thread "Win32 Wanted: Best
>>>>>open source news / mail client."
>>>>
>>>> When a Google Grouper replies to a post, Google collapses multiple
>>>> whitespaces
>>>
>>> Wait - is it Google, or is it any web browser? Isn't multiple
>>> whitespace on a webpage usually striiped by all browsers?
>>
>> I wouldn't have thought any browser would automatically strip any
>> content from a web page - apart from stuff that it can't display, or
>> stuff which the user has deliberately configured to be blocked. A
>> text space is just another text character.
>>
>
> Browser does not strip the contents (whitespaces). It just does not
> display all "characters" - see the Shark's example.

Yeah, the *correct* one: /stuff/

Not the link to the Proxomitron that I accidentally first posted. :)

> Google is complicating (f*g up) the life. Search on MID is send back
> with tags PRE /PRE around the message. That means the browser will
> display all "extra" whitespaces, ., Wanted: Best open

Note to the Whiskery One: the

 element reproduces text exactly as

it was written, including (at least in simple terms) white space.  As

another example, If you look at my usenet bonehead page (no, not the

Google Grouper page; the other bonehead page), you'll see that all of

the entries are in 
 elements, and if someone wrote



help!!!!1!!!!!!!       I'm an idiot!!!!!



Those multiple spaces woudl be rendered.



 



 /comp/ 



In fact, the very first entry shows this quite well.





-- 

Blinky                                                   RLU 297263 

Killing all posts from Google Groups.

Except in Thunderbird, which can't filter that well.

The Usenet Improvement Project:  /comp/