X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f996b,7d021739a2bc70a
X-Google-Attributes: gidf996b,public
X-Google-ArrivalTime: 2001-10-28 15:57:31 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!193.162.153.118!news.tele.dk!not-for-mail
Reply-To: "CeeJay" <newsgroups (at) ceejay.cjb.net>
From: "CeeJay" <newsgroups@ceejay.cjb.nOt>
Newsgroups: alt.ascii-art
References: <y44g084dbav.fsf@nestle.ai.mit.edu>
 <3bdb2fd1$0$216$edfadb0f@dspool01.news.tele.dk>
 <3bdb325c$0$226$edfadb0f@dspool01.news.tele.dk>
 <3bdb3352$0$258$edfadb0f@dspool01.news.tele.dk>
 <9rfe2v$t7k98$1@ID-102694.news.dfncis.de>
 <3bdb45ee$0$230$edfadb0f@dspool01.news.tele.dk>
 <y44snc42jxh.fsf@nestle.ai.mit.edu> <1004282118.43507@queeg.ludd.luth.se>
 <3bdc643e$0$723$edfadb0f@dspool01.news.tele.dk>
 <Pine.GSO.4.33.0110282313480.6390-100000@mpqgrav5.amp.uni-hannover.de>
Subject: Re: How to sort out an ASCII diagram. Boston Public Library floor
 plan.
Date: Mon, 29 Oct 2001 00:57:37 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Lines: 19
Message-ID: <3bdc9b6b$0$750$edfadb0f@dspool01.news.tele.dk>
Organization: TDC Internet
NNTP-Posting-Host: 62.243.165.90
X-Trace: 1004313451 dread04.news.tele.dk 750 62.243.165.90
X-Complaints-To: abuse@post.tele.dk
Xref: archiver1.google.com alt.ascii-art:9193

> > I agree .. <TT>'s SHOULD not be needed .. and adding them makes it incorrect HTML
> > according to the standard.
> > HOWEVER not adding them will cause the ascii to display incorrectly in bad browsers.
> [...]
>
> I'll bite. Which "bad browsers" exactely are we talking about?
>
> Just curious.

To tell you the truth .. I forgot.
I think I first saw the bug with a old IE 3 .. or maybe netscrape 3 , I've had reports
that some old mac browsers did this too .. maybe the IE mac version.
But it does (did) happen .. I have seen it with my own eyes and remember working to find a
solution (found it in the TT's)

None of my currently browsers show this bug.. but I only run two :
IE 6 & Mozilla 9.5 (a somewhat up-to-date nightly build)