X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fd588,f04105921e11bfd4 X-Google-Attributes: gidfd588,public From: mmiicc@dataweb.nl (miK) Subject: Re: tapdance - new Javascript ASCII-animation Date: 1999/05/08 Message-ID: <37347a67.11870558@NEWS.DATAWEB.NL> X-Deja-AN: 475581183 References: <372F6FCE.36D6@iNOdirect.ca> <3730bde0.3409877@NEWS.DATAWEB.NL> <37317FA2.52E0@iNOdirect.ca> <37339aee.20679253@NEWS.DATAWEB.NL> <373432BC.6604@iNOdirect.ca> X-Complaints-To: abuse@nl.uu.net X-Trace: zonnetje.NL.net 926185604 4712 193.78.237.138 (8 May 1999 17:46:44 GMT) Organization: UUNET-NL (http://www.nl.uu.net) NNTP-Posting-Date: 8 May 1999 17:46:44 GMT Newsgroups: alt.ascii-art.animation llizard wrote: >In article <37339aee.20679253@NEWS.DATAWEB.NL>, mmiicc@dataweb.nl (miK) >wrote: >> >> llizard wrote: >> >> [emergency snip] >> >> >I have changed my template to remove any reference to /r/n that was in >> >there before. (It was an earlier version of MSIE that caused us to even >> >add the extra /r in the first place.) >> >> Oops! I didn't know you had changed the code (haven't read the last >> part of the thread "Advanced Ascii Animation - NEW [1/1]") :(( >> >> First the good news: Your modified script _does_ work in MSIE4 on >> Windows95 (that's the platform I used to watch your tapdance). >> The bad news is it's no good in MSIE4 on a Mac! Boxes instead >> of line breaks. >> >> Felt pretty bad about handing over false information. So with >> the device "Thou shalt not extrapolate!" in mind, I ran the 4 >> possible scripts -- using \n, \r, \n\r and \r\n (not /r/n!!) -- >> on the 3 OS'es that I have at my disposal, and drew a >> conclusion, just based on "trial & error". =) > >Hmmm. /r/n was a dyslexic typo in the post only. Sorry about that. I'm >positive that I have never used it in the animations themselves. Yep! That would have struck. >> Here are the results: >> \n \r \n\r \r\n >> msie4.0 (windows) + + - 3) + >> ns4.04 (windows) + + - 3) + >> msie4.01 (mac) - 1) + - 2) + >> ns4.5 (mac) + + - 3) + >> ns4.05 (linux) + + - 3) + >> >> sidenotes 1) no line breaks >> 2) boxes >> 3) extra blank lines >> >> It's either \r or \r\n I guess. But \n isn't that bad. >> >> ~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o >> >> About the remarks made by Matthew Thomas and Martin Atkins... >> >> Matthew -- using ns4.5 (mac) -- noticed extra blank lines. I didn't. >> ...?? No offence, llizard, but did you by accident put in \n\r >> instead of \r\n? >> >> Martin suspected the problems had something to do with the different >> ways dos/windows, un*x/linux and mac treat the end of a line. He made >> his remarks with this diagram in mind, probably: >> >> systems ____end-of-a-line______ ........... >> ascii hex acr | javascript >> dos&windows #13#10 0D 0A CR/LF | \r\n ? >> un*x&linux #10 0A LF | \n ? >> mac #13 0D CR | \r ? >> >> [out of RAM snip] >> >> >I have changed my template to remove any reference to /r/n that was in >> >there before. (It was an earlier version of MSIE that caused us to even >> >add the extra /r in the first place.) >> >> Was that the reason? But we couldn't even find a way to adjust a >> fixed-width font to the anims in MSIE3... > >Thanks for doing the tests, Mic, but... > > ___ / Oh Woe is me! > _/ | \_,v=--- > |_____| _/< ' > --- == > ' > [_____] __>,^ ' >ejm | | //| | > >I can't stand it. I will change everything to \r instead of \n. That's drastic! Are you sure? With \n you've probably got over 90% of the "audience" covered. And, although \r was OK in netscape/linux, I have no idea whether it works on un*x systems as well. Another result to add to the list: \n \r \n\r \r\n ns3.01gold (windows) + + - 3) + >And no, >I'm pretty sure that I didn't put \n\r instead of \r\n. (no offense >taken) Matthew wasn't the only person who was getting double spacing. I >guess it must have been the Mac that caused the addition of the \r. That would be odd. In any case it's probably not a wrapping problem as Matthew suggests, because the default in a