Original Usenet thread from alt.ascii-art, started 13 Apr 1998.
_ _ _ _ _ _ | | | |___ ___ _ __ ___| |_ / \ _ __ ___| |__ (_)_ _____ | | | / __|/ _ \ '_ \ / _ \ __| / _ \ | '__/ __| '_ \| \ \ / / _ \ | |_| \__ \ __/ | | | __/ |_ / ___ \| | | (__| | | | |\ V / __/ \___/|___/\___|_| |_|\___|\__| /_/ \_\_| \___|_| |_|_| \_/ \___|
The <PLAINTEXT> HTML tag: Good for ASCIIArt?
alt.ascii-art
· 30 messages · 13 Apr 1998 - 12 May 1998
I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT>
tag works really well, It means you can have an HTML with the equivilant of a text file at the end,
no markup and no < and > required.
I was wondering if there are any browsers where this doesn`t work?
I`ve attached an example, but outlook express and whatnot may interpret it as the message which
could be quite annoying (I`ve havd it happen to me before when I was emailed an HTML file - MSIE3
mail thought the HTML file was a rich email message! :)
Can you let me know how well this works in Lynx especially, since this was the browser that has
most problems with the asciis in my gallery right now (which, incidentally, I will update soon
I promise!)
_______
/ | | | |\ /| | \
/ | | | | \ / | | \
< |----| | | V | | >
\ | | | | | | /
\ | | | | | |_____ /
(I hate the way Vs are done in the FixedSys font!)
""""""""""""""""""7
Cya........ /
________________/
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
Martin Atkins wrote: > > I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT> > tag works really well, It means you can have an HTML with the equivilant of a text file at the end, > no markup and no < and > required. Hrmm, I use <pre> -- what's the diff? -- _- BluePard ;' )\_ ___ "A foot falls, yet makes no sound...." | ```` \ .-. http://www.geocities.com/southbeach/palms/2115 (\| / ( _)\ //`-` _-'_.' "---' `---'
In article <353...@news.vossnet.net>, zne...@ovtsbbg.pbz (Martin Atkins) wrote: > > I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT> > tag works really well, It means you can have an HTML with the equivilant of a text file at the end, > no markup and no < and > required. > > I was wondering if there are any browsers where this doesn`t work? > > I`ve attached an example, but outlook express and whatnot may interpret it as the message which > could be quite annoying (I`ve havd it happen to me before when I was emailed an HTML file - MSIE3 > mail thought the HTML file was a rich email message! :) > > Can you let me know how well this works in Lynx especially, since this was the browser that has > most problems with the asciis in my gallery right now (which, incidentally, I will update soon > I promise!) > _______ > / | | | |\ /| | \ > / | | | | \ / | | \ > < |----| | | V | | > > \ | | | | | | / > \ | | | | | |_____ / > (I hate the way Vs are done in the FixedSys font!) > [snip] > |_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins| > |_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ | > : _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com| [snip] > : http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | : > : http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | : > '------------------------------------------------------------------------' > If you are new to the newsgroup, please read our FAQ list - posted weekly > and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm It seems to be working in Lynx (I'm amazed) but you might want to add an alt tag to the images you use for your links. For instance, on the teen page, the image "index" appears as "link" in Lynx. How annoying for me that the plaintext tag seems to work for you. I spent hours changing all of my < to < etc, etc, NOTE: If you hit the reply button, add an "e" to the "freent"; its absense is to stop the torment of automatic mailers. -- ha llizard aka ejm cq5...@freenet.toronto.on.ca ^^^^%--- ha www.geocities.com/SoHo/Studios/9334/ " \ ha ASCII-art and Javascript ASCII-animations
Martin Atkins wrote: > > I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT> > tag works really well, It means you can have an HTML with the equivilant of a text file at the end, > no markup and no < and > required. > > I was wondering if there are any browsers where this doesn`t work? Martin, I use <pre> instead also, it seems to be the same. Hmmm? Neither one does much for centering though. *S* Donovan -- __ ( o> Poems By Donovan - http://www.geocities.com/Paris/LeftBank/6558/ ///\ _ _ _ _ _ _ _ _ \V_/_ ___|_|_____|_|_____|_|_____|_|_____|_|_____|_|_____|_|_____|_|__ Home of DA QUIZ! and the famous Secret Link Game. Find and Conquer the Secret Link and win a homepage award. ICQ# 812836 E-Mail:bak...@gwtc.net `````````````````````````````````````````````````````````````````````` (".___.") EVANS PLUNGE BEANIE BABIES PRICE LIST _ { + } _ ()__|>o<|__() http://www.gwtc.net/~bakd/bb.html ( . ) (_) (_) New and Retired Beanies are available!!!
In article <353...@news.vossnet.net>, zne...@ovtsbbg.pbz wrote: > I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT> > tag works really well, It means you can have an HTML with the equivilant of a text file at the end, i like to use the <pre> tag, there is also the <code> tag, both from html 1 so everything should accept them. samples of both: (from your site, natch) <pre> PRE: ___ |---| |_|_| | | | | | | | | | | |___| /_____\ |11:10| |_____| |.....| |.....| \ ___ / | | | | | | | . | | . | | . | mga | . | | . | | . | | . | | . | | | \ / </pre> <code> CODE: ___ |---| |_|_| | | | | | | | | | | |___| /_____\ |11:10| |_____| |.....| |.....| \ ___ / | | | | | | | . | | . | | . | mga | . | | . | | . | | . | | . | | | \ / </code> -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading
Martin Atkins (zne...@ovtsbbg.pbz) wrote: : I`ve been experimenting with ways to display the asciis on my websites, : and I think the <PLAINTEXT> tag works really well, It means you can : have an HTML with the equivilant of a text file at the end, no markup : and no < and > required. 1. Your lines were too long, I had to reformat them for 80col. 2. The <PLAINTEXT> tag is obsolete. Use <PRE> instead. 3. Your pics are fine if your just remember to substitute the < etc. 4. As for the rest of the site, it's awful both in Lynx and as source. If you must use a HTML editor instead of doing it yourself, get a better editor. (I can't comment on how it looks on graphical browsers, but bright yellow on black isn't really my favorite color scheme..) 5. I might try to redo your index page by hand, but first I'll have to make sense of the tag soup it is now.. :( 6. For HTML reference try http://www.w3.org/ and http://www.htmlhelp.com/ In conclusion, most "WYSIWYG" HTML editors I've seen suck large boulders through several kilometers of garden hose, and yours seems to be no exception to the rule. -- __,,,------._ ,-/| `-. Ilmari Karonen (ilt...@sci.fi) ^ All opinions expressed /, '\, `. ,|"-;;.__ http://www.sci.fi/~iltzu/ | in this message are my / ' 4(_,-_,-"_,/.' `'--' ,------------------------' own. If you want me to "`-(_,-"" `-' (,' itz | make some for you too, you should pay for them!
Ilmari Karonen wrote in message <6h2718$eja$2...@tron.sci.fi>... >Repeat after me: *The* *tag* *for* *ascii* *art* *is* *<PRE>!* <!-- evil HTML --> <IFRAME src="asciiimage.txt" type="text/plain" width="about 50" height="about 50"> If you can't see this, you have a frames-impaired browser like Netscape or Lynx.<br> Use <a href="asciiimage.txt">this link</a> to see the picture! </IFRAME> <!-- </evil> --> Of course that's what W3 wants you to use, rather than using ASCIIart in pages because of their accessibility bits. (Or "OBJECT" instead of "IFRAME".) What would be ideal is to use "text/asciiart" but my browser doesn't recognize it (and doesn't display it. Grr.) >>BKNambo -- and that's just the way it is...
fpr...@yahoo.com wrote: : i like to use the <pre> tag, there is also the <code> tag, both from : html 1 so everything should accept them. : samples of both: (from your site, natch) : <pre> [schnip] : </pre> This one should be just fine. : <code> [schnap] : </code> Bzzt, wrong! I might have to dig out my HTML lecture again and post it, but meanwhile here is how a browser would render that. Yes, it will most likely be in a monospaced font, but all the whitespace will still be collapsed: CODE: ___ |---| |_|_| | | | | | | | | | | |___| /_____\ |11:10| |_____| |.....| |.....| \ ___ / | | | | | | | . | | . | | . | mga | . | | . | | . | | . | | . | | | \ / Besides, if that's what you really want, the correct tag would be <TT>. <CODE> is a semantic tag for marking up program code, and nothing else. Repeat after me: *The* *tag* *for* *ascii* *art* *is* *<PRE>!* -- __,,,------._ ,-/| `-. Ilmari Karonen (ilt...@sci.fi) ^ All opinions expressed /, '\, `. ,|"-;;.__ http://www.sci.fi/~iltzu/ | in this message are my / ' 4(_,-_,-"_,/.' `'--' ,------------------------' own. If you want me to "`-(_,-"" `-' (,' itz | make some for you too, you should pay for them!
Ilmari Karonen wrote: > > fpr...@yahoo.com wrote: > [snip] > : <code> > [schnap] > : </code> > > Bzzt, wrong! I might have to dig out my HTML lecture again and post > it, but meanwhile here is how a browser would render that. Yes, it > will most likely be in a monospaced font, but all the whitespace will > still be collapsed: > > CODE: ___ |---| |_|_| | | | | | | | | | | |___| /_____\ |11:10| |_____| > |.....| |.....| \ ___ / | | | | | | | . | | . | | . | mga | . | | . | > | . | | . | | . | | | \ / Curious. I'm using Netscape Communicator 4.05 and both versions rendered identically. I'm sure this doesn't apply to all browsers, just another data point here. Now that I think <hah!> about it, I'm going to use trn for this group instead. cheers, cb Cyberspace Buddha /(0\ What's on, your mind? mailto:c...@io.com \1)/ http://www.io.com/~cb Not your fathers buddha.
On 15 Apr 1998 11:52:08 GMT, ilt...@sci.fi (Ilmari Karonen) wrote: %fpr...@yahoo.com wrote: %: i like to use the <pre> tag, there is also the <code> tag, both from %: html 1 so everything should accept them. %: samples of both: (from your site, natch) % %: <pre> % [schnip] %: </pre> % %This one should be just fine. % %: <code> % [schnap] %: </code> % %Bzzt, wrong! I might have to dig out my HTML lecture again and post %it, but meanwhile here is how a browser would render that. Yes, it %will most likely be in a monospaced font, but all the whitespace will %still be collapsed: % %CODE: ___ |---| |_|_| | | | | | | | | | | |___| /_____\ |11:10| |_____| %|.....| |.....| \ ___ / | | | | | | | . | | . | | . | mga | . | | . | %| . | | . | | . | | | \ / % %Besides, if that's what you really want, the correct tag would be <TT>. %<CODE> is a semantic tag for marking up program code, and nothing else. % %Repeat after me: *The* *tag* *for* *ascii* *art* *is* *<PRE>!* % Ilmari you're right. I think this is something worthy of placing in the FAQ itself as it's quite useful information for newcomers to have. Does anyone else agree? -r- -- enq...@npvq.bet RaD Man % ACiD Productions Founder % Artpacks Archive Founder Words to live by: " It's better to be controversial for the right reasons, than to be popular for the wrong reasons. "
Donovan <bak...@gwtc.net> wrote: >Martin Atkins wrote: >> I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT> >> tag works really well, It means you can have an HTML with the equivilant of a text file at the end, >> no markup and no < and > required. >> I was wondering if there are any browsers where this doesn`t work? >Martin, >I use <pre> instead also, it seems to be the same. Hmmm? Neither one >does much for centering though. *S* With <pre> you still have to use < of course. I thought <plaintext> didn't do anything but suppress HTML interpretation, so that you would have to do <pre><plaintext> ASCII art </plaintext></pre> (of course, it doesn't work the other way around since the <pre> won't work inside the <plaintext>...) John Savard
RaD Man [ACiD Founder] wrote: > > On 15 Apr 1998 11:52:08 GMT, ilt...@sci.fi (Ilmari Karonen) wrote: > % > %Repeat after me: *The* *tag* *for* *ascii* *art* *is* *<PRE>!* > % > > Ilmari you're right. I think this is something worthy of placing in the FAQ > itself as it's quite useful information for newcomers to have. > > Does anyone else agree? > > -r- > > -- enq...@npvq.bet > > RaD Man % ACiD Productions Founder % Artpacks Archive Founder > > Words to live by: " It's better to be controversial for the > right reasons, than to be popular for the wrong reasons. " I second that one....LOL I didn't even know it was an issue, but it's good info. Donovan -- __ ( o> Poems By Donovan - http://www.geocities.com/Paris/LeftBank/6558/ ///\ _ _ _ _ _ _ _ _ \V_/_ ___|_|_____|_|_____|_|_____|_|_____|_|_____|_|_____|_|_____|_|__ Home of DA QUIZ! and the famous Secret Link Game. Find and Conquer the Secret Link and win a homepage award. ICQ# 812836 E-Mail:bak...@gwtc.net `````````````````````````````````````````````````````````````````````` (".___.") EVANS PLUNGE BEANIE BABIES PRICE LIST _ { + } _ ()__|>o<|__() http://www.gwtc.net/~bakd/bb.html ( . ) (_) (_) New and Retired Beanies are available!!!
.----- On Thu, 16 Apr 1998 19:39:33 GMT, John Savard posted:
|<pre><plaintext>
|ASCII art
|</plaintext></pre>
|
'-------------------
Don`t forget: No HTML interpretation, no ending tag... once you use <plaintext> that`s what you`re
stuck with until the end of the document :)
<H1>ASCII art</H1><HR>
<plaintext>
ASCII art
and the plaintext must then remain active until the end of the HTML, so your example will display
a bit like this... (start super ascii web browser <g>)
.------------------------------------------------.
| HyperWeb version 2 [_][O] [X]|
|-------------------------------------------+----|
|.-----. .-----. .-----. .-----. .-----. | |
||<PREV| |NEXT>| |HOME!| |FIND!| |STOP!| | |
|'-----' '-----' '-----' '-----' '-----' +----|
|------------------------------------------------|
| Address: [___________________________________] |
|------------------------------------------------|
| ASCII art |
| </plaintext></pre> |
| |
| |
| |
|------------------------------------------------|
|Ready. [?]|
'------------------------------------------------'
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
.----- On Fri, 17 Apr 1998 11:35:26 GMT, I posted:
|.----- On 14 Apr 1998 18:23:04 GMT, Ilmari Karonen posted:
||
||In conclusion, most "WYSIWYG" HTML editors I've seen suck large boulders
||through several kilometers of garden hose, and yours seems to be no
||exception to the rule.
||
|'----------------------------------
|
|hehe - the 'tag soup' as you put it has been mentioned to me a while ago, and I am no longer using
|the editor, but as the Ascii Gallery hasn`t been updated since then (<g>) it`s still using the
|messy HTML. My other ascii site is done in NotePad, so works a bit better.
|
'-----------------------
Ahh - you were talking about my index page wern`t you <g>
Yes, that was done with the editor ... thanks for the stylesheet enabled version :)
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
.----- On 15 Apr 1998 11:52:08 GMT, Ilmari Karonen posted:
|: <code>
| [schnap]
|: </code>
|
|Bzzt, wrong! I might have to dig out my HTML lecture again and post
|it, but meanwhile here is how a browser would render that. Yes, it
|will most likely be in a monospaced font, but all the whitespace will
|still be collapsed:
|
|CODE: ___ |---| |_|_| | | | | | | | | | | |___| /_____\ |11:10| |_____|
||.....| |.....| \ ___ / | | | | | | | . | | . | | . | mga | . | | . |
|| . | | . | | . | | | \ /
|
'--------------------------
I agree that <code> is for code, but surely it should render like <pre> so that the indents
and the like remain?
<PRE>
|||||
| o o | .--- Ohh! I have a character entity stuck to my face!
| > | / and my speech line is dislodged too!
| \_/ | ----'
\___/
__| |__
/ \_/ \
| | | |
| |MGA| |
| | | |
</PRE>
I should imagine that Llizard will look very strange with all those < and >s! :)
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
.----- On 14 Apr 1998 18:23:04 GMT, Ilmari Karonen posted:
|
|In conclusion, most "WYSIWYG" HTML editors I've seen suck large boulders
|through several kilometers of garden hose, and yours seems to be no
|exception to the rule.
|
'----------------------------------
hehe - the 'tag soup' as you put it has been mentioned to me a while ago, and I am no longer using
the editor, but as the Ascii Gallery hasn`t been updated since then (<g>) it`s still using the
messy HTML. My other ascii site is done in NotePad, so works a bit better.
What I was saying about <PLAINTEXT> is that it allows you to basically have a text file that uses
colours and a big heading at the start - and the < and >s arn`t necesary :)
If it`s obsolete, I`ll just stick with <PRE> :)
Cya,
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
.----- On Mon, 13 Apr 1998 19:05:11 -0400, BluePard posted:
|Hrmm, I use <pre> -- what's the diff?
'---------------------------
<PLAINTEXT> defines the rest of the document as plain text (ie no tags) so you can just litterally
paste in any text file and it will display exactly, using the colours and title specified in the
<BODY> and <HEAD> tags.
However, it appears to be obselete so it seems it`s not a good idea to use it.
Back to my <-ing session.... :)
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
Donovan (bak...@gwtc.net) wrote: > Martin Atkins wrote: > > > > I`ve been experimenting with ways to display the asciis on my websites, and I think the <PLAINTEXT> > > tag works really well, It means you can have an HTML with the equivilant of a text file at the end, > > no markup and no < and > required. > > > > I was wondering if there are any browsers where this doesn`t work? > Martin, > I use <pre> instead also, it seems to be the same. Hmmm? Neither one > does much for centering though. *S* <pre> works fine, but it requires < and > You can center your ASCII art if you do all lines with the same size filling with blanks. <PLAINTEXT> is something I've never used ... I bet it's some new feature not accepted with every browser! Anti-spam measure: remove the scalp to reply by email -- _____ _____ ______ __ -/\ __\---/\ __\---/\ __ \---/\ \---------------------------------------- -\ \ \_/_--\ \ \_/---\ \ \_\ \--\ \ \-------------- Armando Frazao --------- --\ \___ \--\ \ _\---\ \ __ \--\ \ \----- http://alfa.ist.utl.pt/~l33812 - ---\/ __\ \--\ \ \/__--\ \ \/\ \--\ \ \____--- L33812 @ alfa.ist.utl.pt ---- -----/\____\--\ \____\--\ \_\ \_\--\ \_____\-------------------------------- -----\/____/---\/____/---\/_/\/_/---\/_____/-------------------- 1995 IST --
Seal do Mar wrote in message <6ha7n8$vu1$1...@ci.ist.utl.pt>... > <PLAINTEXT> is something I've never used ... I bet it's some new >feature not accepted with every browser! From what I've heard so far, <PLAINTEXT> is actually a very old feature not accepted with every browser (anymore). >>BKNambo -- and that's just the way it is...
On Sat, 18 Apr 1998 22:39:16 -0400, "Brock Kevin Nambo" <new...@earthling.net> wrote: >Seal do Mar wrote in message <6ha7n8$vu1$1...@ci.ist.utl.pt>... >> <PLAINTEXT> is something I've never used ... I bet it's some new >>feature not accepted with every browser! > From what I've heard so far, <PLAINTEXT> is actually a very old feature not >accepted with every browser (anymore). > I have heard of BLOCKQUOTE or something like that. (Too lazy to get the html code book out) Does that work? I have no idea how old it is. Laura S=- .- -. -=S SheDragon at globalserve dot net H /( )\ H E | -^^- | E The universe is full of magical things \_ `' _/ patiently waiting for our wits to grow sharper. S \ ) S - Eden Phillpots H )/ H E=- (' -=E (ASCII Art by Rik Downing)
SheDragon wrote in message <353...@news.globalserve.net>... >On Sat, 18 Apr 1998 22:39:16 -0400, "Brock Kevin Nambo" ><new...@earthling.net> wrote: > >>Seal do Mar wrote in message <6ha7n8$vu1$1...@ci.ist.utl.pt>... >>> <PLAINTEXT> is something I've never used ... I bet it's some new >>>feature not accepted with every browser! >> >From what I've heard so far, <PLAINTEXT> is actually a very old feature not >>accepted with every browser (anymore). >> > > >I have heard of BLOCKQUOTE or something like that. (Too lazy to get >the html code book out) Does that work? I have no idea how old it is. BLOCKQUOTE is a current tag (It's in HTML4.0 even), but I don't believe it does monospaced or preservation of < > & etc. It's meant to mark up a large quoted division, as opposed to the inline <Q> tag (which does nothing in either IE or Netscape, but is supposed to put quotes around the text). >>BKNambo.html -- and that's just the way it is...
SheDragon wrote in message <353...@news.globalserve.net>... >On Sat, 18 Apr 1998 22:39:16 -0400, "Brock Kevin Nambo" ><new...@earthling.net> wrote: > >>Seal do Mar wrote in message <6ha7n8$vu1$1...@ci.ist.utl.pt>... >>> <PLAINTEXT> is something I've never used ... I bet it's some new >>>feature not accepted with every browser! >> >From what I've heard so far, <PLAINTEXT> is actually a very old feature not >>accepted with every browser (anymore). >> > > >I have heard of BLOCKQUOTE or something like that. (Too lazy to get >the html code book out) Does that work? I have no idea how old it is. BLOCKQUOTE is a current tag (It's in HTML4.0 even), but I don't believe it does monospaced or preservation of < > & etc. It's meant to mark up a large quoted division, as opposed to the inline <Q> tag (which does nothing in either IE or Netscape, but is supposed to put quotes around the text). >>BKNambo.html -- and that's just the way it is...
Martin Atkins (zne...@ovtsbbg.pbz) wrote:
: I agree that <code> is for code, but surely it should render like
: <pre> so that the indents and the like remain?
No, not really. If you wanted to be pedantic, the correct markup
would be:
<PRE><CODE>
#include <stdio.h>
void main( void )
{
printf( "Hello World!\n" );
}
</CODE><PRE>
However, this is what the HTML 2.0 specification says: (The later ones
say much the same thing.)
The CODE element indicates an example of code, typically rendered
in a mono-spaced font. The CODE element is intended for short words
or phrases of code; the PRE block structuring element (section
Preformatted Text: PRE) is more appropriate for multiple-line
listings. For example:
<P>The expression <CODE>x += y</CODE> is shorthand for <CODE>x = x
+ y</CODE></P>
And this is from the CSS implementation of the default rendering of
HTML 2.0:
H1, H2, H3, H4, H5, H6, P, UL, OL, DIR, MENU, DIV,
DT, DD, ADDRESS, BLOCKQUOTE, PRE, BR, HR { display: block }
B, STRONG, I, EM, CITE, VAR, TT, CODE, KBD, SAMP,
IMG, SPAN { display: inline }
[snip]
PRE, TT, CODE, KBD, SAMP { font-family: monospace }
PRE { white-space: pre }
And since I was digging around the old DTDs anyway, I thought I'd find
some info about <PLAINTEXT>. I found out that HTML 2.0 defines it as
a _deprecated_ element, and absolutely refuses to describe it outside
of the SGML declaration.
It turns out that its content model is indeed defined as CDATA, which
means that everything between it and the first </PLAINTEXT> is treated
literally. The same definition is given for <XMP> and <LISTING>, which
are described in the document and are already considered deprecated in
favor of <PRE>.
However, it seems that the original (HTML 1.0) definition was probably
different, in that _everything_ after <PLAINTEXT> was treated literally
until the end of the document. I couldn't find a copy of HTML 1.0 to
verify this, but I did find this piece of a message at
http://www.acl.lanl.gov/HTML_WG/html-wg-95q2.messages/0020.html
a) HTML 2.0 is a definition of existing practice in mid-1994 and
b) HTML UA's accepted and processed XMP, LISTING and PLAINTEXT at
that date, and
c) These constructs, (PLAINTEXT in particular) are not SGML compliant,
and
d) These constructs were in the HTML 1.0 specifications, and
Oh, and one more funny thing about <PLAINTEXT>. Apparently HTML 2.0
does _not_ define it as a block-level element (inside <BODY>) like
<PRE> (and <XMP> and <LISTING>) but as a special part of a document
_outside_ <HEAD> and <BODY>, much like <FRAMESET> in later standards.
So, why all this? I think the reason was HTTP 0.9, a very primitive
protocol which did not support "Content-Type:" (or any headers at all
for that matter). So everything retrieved over HTTP 0.9 was assumed to
be HTML, and if you wanted to put plain text on the web in those days
you had to stick <PLAINTEXT> on the first line.
--
. _, .. j u s t. h o w l.i n g i n .t h e n.i g h t .. ._, .
, )'' . /\_ . ' ,/\ . , ``( ,
_\__/ |__.'\._______,--;_'_`-.___,.______,/_,_`.__,-.__'__,/`-._,_| \____
,_f_)\. Ilmari Karonen ilt...@sci.fi http://www.sci.fi/~iltzu/ /(_|_,.
On 18 Apr 1998 12:52:56 GMT, Seal do Mar <l33...@alfa.ist.utl.pt> wrote: > <pre> works fine, but it requires < and > > You can center your ASCII art if you do all lines with the >same size filling with blanks. You can also center <pre> formatted text by putting it in a single celled table: <div align=center> <table> <tr><td> <pre> ascii pics in here </pre> </td></tr> </table> </div> Joseph Abbott "I can picture in my mind a world without war, a world without hate. And I can picture us attacking that world, because they'd never expect it." - Deep Thoughts __
Joseph Abbott (jabbott@{remove}lynx.bc.ca) wrote:
: You can also center <pre> formatted text by putting it in a single
: celled table:
: <div align=center>
: <table>
: <tr><td>
: <pre>
: ascii pics in here
: </pre>
: </td></tr>
: </table>
: </div>
I'd also add align=left to the PRE. And DIV is indeed better here than
CENTER. (Think of browsers that understand CENTER but neither tables nor
align attributes.)
<div align=center>
<table><tr><td>
<pre align=left>
)
((
|:""|-,
|: |/
'---'
</pre>
</td></tr></table>
</div>
--
Ilmari Karonen (ilt...@sci.fi)
http://www.sci.fi/~iltzu/
Try the <TT> and </TT> tags.
Or <PRE> and </PRE>, too...
--
__--___ ,++----------------------====---,
________|_:_:___\_______ ( || \<=\======NCC-1701==== I I|/
\______________________| `===---------------------------'
\__________/\\:\'\ |:|
\__/ \\:\'\ | |
\\_\_\_____|:|__
. /|| "-... . |_|.L\ Marco Antonio
-+)| =<=== ."...,-' Checa Funcke
' \||______,--' mailto:JTK...@usa.net
mailto:JTK...@HoTMaiL.com
mailto:mch...@li.urp.edu.pe
http://www.GeoCities.com/Hollywood/2645
.----- On 19 Apr 1998 18:48:39 GMT, ilt...@sci.fi (Ilmari Karonen) posted:
|
|So, why all this? I think the reason was HTTP 0.9, a very primitive
|protocol which did not support "Content-Type:" (or any headers at all
|for that matter). So everything retrieved over HTTP 0.9 was assumed to
|be HTML, and if you wanted to put plain text on the web in those days
|you had to stick <PLAINTEXT> on the first line.
|
'-----------------------------
Yup - that`s what my HTML book says :)
.------------------------------------------------------------------------.
:_ _ _ _ :
|_|_ _|_| _ _ _ _ _ _ _|_|_ _ |_| _ _ _ :
|_|_|_|_|_| _|_|_|_| |_|_|_|_| |_|_|_|_| _ |_|_|_|_ :
|_| |_| |_| |_| |_| |_|_| |_| |_| |_| | ||||| .-----------.
|_| |_| |_|_ _|_| |_| |_|_ _ |_| |_| | | o o ||mart.atkins|
|_| _ _ |_| |_|_|_| |_| _ |_|_| |_| |_| | | > || @ |
: _|_|_|_ _|_|_ _ |_| _ |_| _ _ _ _ _ _ | \_/ ||bigfoot.com|
:|_|_ _|_| |_|_|_|_| |_|_|_| _ |_|_|_|_ _|_|_|_| \___/ '-----------'
:|_|_|_|_| |_| |_|_|_ |_| |_| |_| |_|_|_ _ __| |__ :
:|_| |_| |_|_ _ |_| |_|_ |_| |_| |_| _ _|_| / \_/ \ :
:|_| |_| |_|_| |_| |_| |_| |_| |_| |_|_|_| | | | | :
: http://vibes.vossnet.co.uk/i/ighaig/ | |MGA| | :
: http://voices.vossnet.co.uk/a/atkins/ascii.htm | | | | :
'------------------------------------------------------------------------'
If you are new to the newsgroup, please read our FAQ list - posted weekly
and on the web at http://vibes.vossnet.co.uk/i/ighaig/ascfaq.htm
On Sat, 18 Apr 1998 22:39:16 -0400, Brock Kevin Nambo spoke unto the people of alt.ascii-art in these words: > Seal do Mar wrote in message <6ha7n8$vu1$1...@ci.ist.utl.pt>... >> <PLAINTEXT> is something I've never used ... I bet it's some new >> feature not accepted with every browser! > From what I've heard so far, <PLAINTEXT> is actually a very old > feature not accepted with every browser (anymore). Yup. It preceded <PRE>. <PLAINTEXT> was deprecated in HTML 2.0 (in favor of <PRE>), and obsoleted in the HTML 3.0 draft. Liz -- Elizabeth T. Knuth "A cockroach in a tuxedo ekn...@tiny.computing.csbsju.edu is still a cockroach." http://www.users.csbsju.edu/~eknuth/ -Richard K. Bethell, <>< + IXOYE + ><> nanae, 6 Nov 97
JTKirk wrote: > > Try the <TT> and </TT> tags. > Or <PRE> and </PRE>, too... > -- > > __--___ ,++----------------------====---, > ________|_:_:___\_______ ( || \<=\======NCC-1701==== I I|/ > \______________________| `===---------------------------' > \__________/\\:\'\ |:| > \__/ \\:\'\ | | > \\_\_\_____|:|__ > . /|| "-... . |_|.L\ Marco Antonio > -+)| =<=== ."...,-' Checa Funcke > ' \||______,--' mailto:JTK...@usa.net > mailto:JTK...@HoTMaiL.com > mailto:mch...@li.urp.edu.pe > http://www.GeoCities.com/Hollywood/2645 Preferrably the <PRE></PRE> , The <TT></TT> won't show newlines ( NL/CR or whatever...I tend to call them \n ) nor Tabs ( \t )... Scotty, beam me up! -- _ _ ------------\ ,---. /------------ ---------. `-./ "\.-' .--------- --------\ . /-------- ------`-.| .-'------ ---/ `/"\ \--- `//_-_\\' .----------(.'---',)----------. | mailto:ojo...@mindless.com | | http://ojoshiro.neroc.nl | | --oO(_)Oo-- | | Ojoshiro fuit hic | "-----------------------------"
zne...@ovtsbbg.pbz (Martin Atkins) wrote: >.----- On 19 Apr 1998 18:48:39 GMT, ilt...@sci.fi (Ilmari Karonen) posted: >| >|So, why all this? I think the reason was HTTP 0.9, a very primitive >|protocol which did not support "Content-Type:" (or any headers at all >|for that matter). So everything retrieved over HTTP 0.9 was assumed to >|be HTML, and if you wanted to put plain text on the web in those days >|you had to stick <PLAINTEXT> on the first line. >| >'----------------------------- >Yup - that`s what my HTML book says :) And there is no </plaintext> tag, although some browsers recognize it. <xmp> ... </xmp> is used like <pre> but suppresses all tags within it except </xmp>, so that's actually the one to use. John Savard
Related ASCII art in the Gallery
Explore these categories from our collection of 11,000+ artworks:
Make your own ASCII art
Turn images, text or 3D into ASCII, or draw your own – right in your browser.
About this thread.
These messages were posted publicly to the newsgroup
alt.ascii-art
in 1998 and are mirrored here unchanged as part of the Historic Archives – only email addresses are masked.
The artwork and text belong to their original authors: if you copy a piece, keep the artist's initials or signature intact and credit them where you can.
Are you one of the authors? Contact us to get your posts attributed, connected to your artist profile, or removed.
Report this message
Help us keep the archive clean and accurate. Reports are reviewed by a person – nothing is changed automatically.