X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,e8656e8782b25e98 X-Google-Attributes: gidf996b,public X-Google-Thread: f4f4a,aebf519eeed7c8a9 X-Google-Attributes: gidf4f4a,public From: mvcorks@undergrad.math.uwaterloo.ca (Matt Corks) Subject: Re: Ascii-art in HTML Date: 1996/07/28 Message-ID: #1/1 X-Deja-AN: 170993456 sender: news@undergrad.math.uwaterloo.ca (news spool owner) references: <4rigs4$ed5@olorin.nask.pl> <4t7ges$o4m@grivel.une.edu.au> <31F86F4D.4876@stanford.edu> organization: None to speak of. newsgroups: alt.ascii-art,alt.html In article <31F86F4D.4876@stanford.edu>, Michael Silverton wrote: >CRYLUX wrote: > >> Ascii Image came be use just every one has done it wrong so far. >>
  _____
>>  /     \
>> | () () |
>>  \  ^  /
>>   |||||
>>   |||||
>> The Trick is geting the pre in the right place. No fun chars nothing. Hey, cool! Didn't think of that. Thanks! >hmmmmm ... when I use this: [snip] >I get this in Netscape 3.0b5: > >,o888b,`?88888 ,8888 888 ?888 8888888P' 888 888P' > > >And this in Lynx 2.5: > > ,o888b,`?88888 > > ,8888 888 ?888 > > 8888888P' 888 > > 888P' 888 > > `88 O d888 > > `?._ _.o88888 > > >Neither is really optimal. Extra vertical space in Lynx and no > like action in Netscape. I agree that's stupid (as stated in a previous post to this thread). However, I suspect the problem is the actual HTML text file. I just tried this with a UNIX HTML document, and I didn't have a problem. MS-DOS uses as an end of line character, UNIX is , and MacOS is . In the example above, it seems the was screwing it up. Get a text editor that's capable of saving it with as the end of line character, such as the vi emulator vim. -- Matt Corks, 1B Co-Op PMath, C.S. mvcorks@uwaterloo.ca, http://www.csclub.uwaterloo.ca/u/mvcorks "Millport is an island off the coast of Scotland. Sometimes teenagers go there and take LSD." -The Vaselines, describing the song `The Day I Was A Horse'