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: <37339aee.20679253@NEWS.DATAWEB.NL>#1/1
X-Deja-AN: 475384886
References: <372F6FCE.36D6@iNOdirect.ca> <3730bde0.3409877@NEWS.DATAWEB.NL>
 <37317FA2.52E0@iNOdirect.ca>
X-Complaints-To: abuse@nl.uu.net
X-Trace: zonnetje.NL.net 926128366 21889 193.78.237.180 (8 May 1999 01:52:46
 GMT)
Organization: UUNET-NL (http://www.nl.uu.net)
NNTP-Posting-Date: 8 May 1999 01:52:46 GMT
Newsgroups: alt.ascii-art.animation

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". =)

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...

[snip]
>      / ,^^%--- ha    EVENTUALLY, I'll upgrade past NS3....

 :) --mic