Technology evolution and ascii pics
From Pete Casso <pet...@sympatico.ca>
· alt.ascii-art
· 21 May 1998 00:00 · View full thread
· report
This article is a rather long essay without cute pics ;-))
I wrote this essay because some people seem to think that the Outlook Express
issue discussed elsewhere is an isolated one. I do not think that this is an
isolated issue, on the contrary, I think that this is a manifestation of
on-going technology evolution, and more manifestations are sure to come. This
essay is to first describe the on-going technology evolution and to
subsequently suggest what we can do to protect our ascii pics.
Well, enough for the prologue, let's go on with the essay ...
Not so long ago, the world was simple for ascii pics. Whatever you drew, and
as long as you followed a few simple rules, ascii pics will be displayed
correctly by email and newsgroup software.
One of the very fundamental assumptions that makes this simple world work, is
that both the maker and the viewer of the ascii pics use simple, plain
vanilla, text editors. Yes, that right, email and newsgroup software have
built-in text editors. Simple, plain vanilla, text editors ... that is, until
recently ...
=> The simple, plain vanilla, text editors built into email and newsgroup
software are evolving towards more sophisticated word processors <=
These email and newsgroup software with their built-in word processors need to
be sold to the buying public, and therefore need to have features that makes
life easier for the user community at large. One example of such a useful
feature is the automatic elimination of a blank space that a hasty user has
inadvertently left at the beginning of a line. How time consuming, how
user-friendly, how nice!
Well, what is nice for general purpose applications may not be so nice for a
special purpose application such as ascii pics. Automatic elimination of a
blank space can obviously damage an ascii pic.
In time, other word processing features that are useful for general purpose
applications such as automatic conversion to curly/smart quotes, automatic
capitalization, automatic conversion of a top line to a header, etc will make
their way into email and newsgroup software. That means, that in time, email
and newsgroup software are more and more likely to do damage to ascii pics.
This will (slowly) break down the very fundamental assumption that makes ascii
pics work in the simple world alluded to in the above. The maker of the ascii
pic may still use a simple, plain vanilla, text editor. However, more and more
viewers will no longer view ascii pics with simple, plain vanilla, text
editors. More and more viewers will use word processors that will have more
and more features that can cause damage to ascii pics.
This concludes the first part of this essay describing the on-going technology
evolution and how it creates problems for ascii pics.
Let's continue with the second part of the essay and ask ourselves the
question, how do we protect our ascii pics? Or to rephrase the question, how
do we make sure that viewers will see the same pic as the maker of the ascii
pic?
Well, there are short term and long term solutions. Short term solutions look
at email and newsgroup software in actual use and recommend workarounds. An
example of a short term solution is described in the article "Usable pagewidth
for ascii pics" that I recently posted in this newsgroup. The recommended
workaround is not to follow the conventional wisdom of using columns #1 to
#80, but to use a more cautious and narrower pagewidth, from column #3 to
column #73.
What about the long term solutions? How can we protect our ascii pics in this
changing world in the long run?
Well, we need to create a simple world again, where maker and viewer of ascii
pics use essentially the same tools. An example of such a simple world is the
"ascii" on AOL (Just look at the pure technical aspects here, ignore the
cultural/ethical aspects of intellectual property for the moment.) In this
example, both maker and viewer use the proprietary email and newsgroup
software from AOL and it is this simple world again that makes this kind of
"ascii" work (within AOL.)
How about creating a simple world outside of AOL? A simple world that works
for ascii pics for the global Internet?
Unfortunately, we cannot create such a simple world based on word processors,
since there is no standard for word processors. In other words, the built-in
word processors of email and newsgroup software will have bestowed on them
different general purpose "feature" sets, which will damage ascii pics in many
different ways. And to say things more drastically, the more advanced the
"feature" set, the more likely the damage to the ascii pic is going to occur,
and the more extensive the damage to the ascii pic is likely going to be.
However, there is an html standard that we can use to create such a simple
world again, one that works for ascii pics for the global Internet. And, as we
have seen from past discussions in this newsgroup (or were these discussions
more like wars ;-)) all we need is a rather small subset of carefully chosen
html tags to make sure that both maker and viewer see the same ascii pic.
In other words, the maker of the ascii pic provides display instructions in
the form of html tags to the viewing tool, in order to make sure that the
viewing tool displays the ascii pic correctly. This is to be contrasted to the
use of the built-in word processors of email and newsgroup software. As
viewing tools, these word processors work without the benefit of display
instructions (i.e. html tags.) These word processors will try to display the
ascii pic information with the general purpose "feature" set bestowed on them,
which can and will damage ascii pics as we saw in the above.
This concludes the second part of this essay, which describes short term and
long term solutions on how to protect our ascii pics.
Let's continue with the third and last part of this essay (my goodness, when
is this crazy guy going to stop?) on the _timescale_ of this technology evolution.
In other words, when exactly will email and newsgroup software become so
"feature" rich, that they will inevitably do serious damage to ascii pics? Or
to rephrase the question, what is the timescale for html becoming necessary to
ensure undamaged ascii pics?
That is difficult to say, on the one hand, entrenched technologies tend to
live "forever" ... typewrites are still being used. On the other hand,
Internet technologies including email and newsgroup technologies are evolving
at break-neck speeds ... Netscape 4.0.5 that I installed a few days ago has
_html_ as the default option for email and newsgroups, _not) plain text.
However, whereas the timescale is difficult to predict, the trend is clear,
i.e. the need for protecting ascii pics with html (display instructions) is
clearly becoming greater and greater with time.
In summary (holy cow, this guy is indeed a very, very, very disturbed
psychopath, just look at his portrait!) this essay has:
in the first part, described the evolution of email and newsgroup software and
how general purpose "feature" sets of their built-in word processors can and
will do damage to ascii pics;
in the second part, described short term and long term solutions for
protecting ascii pics. Short term solutions are workarounds to prevent
automatic manipulations by the built-in word processors of email and newsgroup
software. An example is the use of columns #3 to #73 only for ascii pics to
prevent damage by Outlook Express for Windows. Long term solutions include the
use of html with its intrinsic set of display instructions in the form of html tags;
in the third and last part, stated that the timescale for this "ascii pic
endangering" technology evolution is difficult to predict, but that the trend
is clear, i.e. towards greater danger and towards greater necessity of
protecting ascii pics with display instructions, presumably in the form of
html tags.
Print this essay out!
Or I will torture you!
Read it on the screen!
/
-. -. `. / .-' _.' _
.--`. `. `| / __.-- _' `
'.-. \ \ | / _.' `_
.-. \ ` || | .' _.-' `.
.' _ \ ' - -' - ` _.-.
.' `. %%%%% | %%%%% _.-.`-
.' .-. ><(@)> ) ( <(@)>< .-.`.
(("`( - | | - )'"))
/ \\#)\ (.(_).) /(#//\
' / ) (( / | | \ )) (`.`.
.' (.) \ .md88o88bm. / (.) \)
/ /| / \ `Y88888Y' / \ | \ \
.' / O / `. - .' \ O \ \\
/ /(O)/ /| `.___.' | \\(O) \
/ / / / | | | |\ \ \ \
/ / // /| | | | \ \ \
_.--/--/'( ) ) ( ) ) )`\-\-\-._ The Dreaded Psychopath Pete Casso
( ( ( ) ( ) ) ( ) ) ( ) ) ) ( ) ) Portrait by Veronica Karlsson
Original message headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,cc07b6bb8d657c99,start X-Google-Attributes: gidf996b,public From: Pete Casso <pet...@sympatico.ca> Subject: Technology evolution and ascii pics Date: 1998/05/21 Message-ID: <356...@sympatico.ca> X-Deja-AN: 355384406 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 NNTP-Posting-Date: Thu, 21 May 1998 19:35:00 EDT Content-Type: text/plain; charset=us-ascii Organization: Frogstein and Birdstein Productions Newsgroups: alt.ascii-art
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 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.