X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f4f4a,aebf519eeed7c8a9
X-Google-Attributes: gidf4f4a,public
X-Google-Thread: f996b,e8656e8782b25e98
X-Google-Attributes: gidf996b,public
From: Biggo <mfasola@dial.eunet.ch>
Subject: Re: Ascii-art in HTML
Date: 1996/07/21
Message-ID: <31F28074.2FA@dial.eunet.ch>#1/1
X-Deja-AN: 169426975
references: <4rigs4$ed5@olorin.nask.pl> <eGi5pFAd$P3xEwWI@xemu.demon.co.uk>
 <0$FNQ0A8h44xEwZG@xemu.demon.co.uk> <4s6c2e$qfd@bad-news.harborcom.net>
content-type: text/plain; charset=us-ascii
organization: Suoni & macchinine, CH-6994 Aranno (ti)
mime-version: 1.0
newsgroups: alt.ascii-art,alt.html
x-mailer: Mozilla 3.0b4 (Macintosh; I; 68K)


Robert Croson, Jr wrote:
> 
> Padding the line with extra spaces and returns and crap won't work. HTML
> is specifically designed to remove ALL EXTRA SPACES AND LINE BREAKS. That
> is why placing control codes will not provide the result you are looking
> for. If <BR> and <P> don't work, you're SOL.

HTML is also specifically designed to respond to <PRE> and </pre>. So what?
Extra spaces DO work. Font size and colour DO work. Return doesn't.
Why are you people replying to this thread if you haven't got a clue?
If you put many spaces (tens, maybe hundreds) after a word, you'll force the
next word on the next line. I did it. It works in Netscape 1, 2 and 3. Stop.

Biggo.
-- 
*** If your car could travel at the speed of light,
    would the headlights still work?            ***