Settings

The page will reload to apply your changes.
Theme

ASCII Art Font

ASCII Art Menu

Original Usenet message from alt.ascii-art, 25 Sep 1998.
Re: About rendering ascii code in a .txt medium

Re: About rendering ascii code in a .txt medium

In article <360...@sympatico.ca>, Pete Casso <pet...@sympatico.ca> writes:
[snip]
|> The RFC 20 tossed up by someone in this thread is probably an invalid trial
|> balloon. It can't be found in the IETF archives, and the other RFCs tossed up
|> by that same someone are irrelevant to this discussion.
RFC20 is listed in the rfc-data.txt as having the title
"ASCII format for network interchange", and is the only RFC that I saw listed
as being relevant - Simply because you could not find the file does not mean
that I made it up [Search for the title I mentioned in the "rfc-data.txt" file
in the same directory as your rfcs are in, and you will indeed see that it is
the title of RFC 20.  If you cannot *find* RFC 20, then you aren't looking hard
enough]

As for the other RFCs I "tossed up", the were SARCASM.  It is perhaps a bit
saddening that you cannot recognize sarcasm without <SARCASM></SARCASM> tags
around it.  The point of mentioning the April Fools RFCs was to compare the
absurd things you were describing with the absurd things in those RFCs.

|> > What you are proposing (letting the artist specify fonts and color, and so
|> > on) does add stuff to the picture, in the form of font tags, color codes, or
|> > whatever the format in question is using.  When that code reacies it's
|> > target (the recipient), it will be displayed, and will be displayed right
|> > only if the recipient has everything the artist has, in the way of
|> > typographical capabilities (this especially includes specific fonts at
|> > specific sizes).
|> 
|> Well, a skillful artist will not use obscure fonts or obscure anything, you
|> can always produce bad things with good tools.
The fact remains, regardless of what fonts the artist uses, the viewer will need
to have those fonts on their computer.

|> Some people are beginning to recognize, that perceived limitations are in
|> reality just barnacles from the past, due to historical and limited
|> implementations. The ascii standard itself imposes no such limitations!
Either give us a quote showing that there are no such limitations,
or concede the argument that the ascii standard limits ascii to the being
7 or 8 bit text in the range 0x20 to 0xFF.

|> > Your views mave no merit at all, if you can't back them with proven facts or
|> > quotations.
|> 
|> My views do have merit, because I did back them up with proven facts and
|> clearly observable trends. (Although I indeed can't post quotes that don't
|> exist ;-)) 
Hmm, I seem to have missed these so called "proven facts" - could you repost
them, along with names and references of who proved them?

|> No, you did not back up the prohibitions, etc that you tossed up, you did not
|> post quotes on the prohibitions, etc from the ascii standard!
And you didn't post a quote from the standard saying that there are no
prohibitions.

|> > My viewes aren't necessarily facts either,
|> 
|> No, they aren't. In particular, there are no such prohibitions, etc in the
|> ascii standard, my friend!
<PITY FOR OBTUSE PETE>
	He obviously *meant* that his views were opinions, not facts,
	whereas you seem to be claiming that you views are facts, not opinions.
</PITY>

|> > When that code reaches the recipient, it is displayed using his or her
|> > default settings (even if they are wrong).
|> 
|> Yes, and these days, that's wrong 20% of the time and getting worse. I wonder,
|> sometimes you recognize this central issue, sometimes you want to discuss it
|> away! See the following quote.
|> 
|> > ASCII art still requires only CODE element.
|> 
|> It is exactly the denial that the other (typographical) code element exist,
|> that is like putting your head in the sand. It is exactly the other code
|> element that causes 20% troubles and becoming worse. The ascii code element
|> itself does not cause any problems.
You are *partially* right - it is a denial that typographical code is part of
the ascii character set;  There are no ascii characters to specify any sort
of typography.  Any type of code that does so specify typography is not ascii.

|> Well, what shall I say, you are probably not in a consumer friendly business,
|> or else you would not ask the viewer to spend any effort, and if they refuse
|> to do so, call them names!
He's not the one trying to promote some new definition of an old term, so he's
allowed to call lazy people "lazy" if he wants to.


|> > You know it's capabilities all right, but you are confusing them with the
|> > capabilities that other media (such as HTML) offer.  ASCII alone, without
|> > all the markup tags and crap, is capable of displaying some very good
|> > artwork, and conveying most any idea you want, but not much beyond that.
|> 
|> Almost right, but I am not confusing anything, I just don't pull the plug that
|> quickly on ascii's capabilities.
How is "ASCII alone ... is capable of displaying some very good artwork ..."
pulling the plug on ASCII's capabilities?

|> 
|> > And it is that low amount of capability (compared to other media) that
|> 
|> Just don't pull the plug that quickly, and you too will see ascii's tremendous
|> capabilities. Try it, you won't be disappointed as a pioneer, I can assure you!
You must be thinking of something other than ascii - simply by writing his message
to usenet is a use of ascii.  What is it that you want him [and the rest of us, I
assume] to do with ascii that we're not already doing?

|> 
|> =========================================================
|> []   .oo     Visit the Gallery of the 'steins!         []
|> []  (  -)   http://www3.sympatico.ca/petecasso/        []
|> []   " "   Frogstein, who has a point behind his eyes  []
|> =========================================================
-- 
Ben Goldberg
--
Trespassers will be shot.  Survivors will be prosecuted.

Original message headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f996b,de3737aab10fae64
X-Google-Attributes: gidf996b,public
From: gol...@cii3130-22.rcs.rpi.edu (Benjamin Goldberg)
Subject: Re: About rendering ascii code in a .txt medium
Date: 1998/09/25
Message-ID: <6uf8e3$7p...@cii3130-22.rcs.rpi.edu>
X-Deja-AN: 394626204
References: <Pin...@onyx.southwind.net> <360...@sympatico.ca> <6u9edj$9e...@vccsouth-21.rcs.rpi.edu> <360...@sympatico.ca> <Pin...@onyx.southwind.net> <360...@sympatico.ca> <Pin...@onyx.southwind.net> <360...@sympatico.ca>
Organization: Rensselaer Polytechnic Institute, Troy, NY.
Newsgroups: alt.ascii-art
About this message. This message was posted publicly to the newsgroup alt.ascii-art in 1998 and is 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 the author? 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.

Help classify this post