The old saying of a picture is worth a 1000 words can be quite true.
I'd like to point out that the IETF's RFC have been distributed as plain text since 1969. The few images that are present are ASCII, fixed font width images.
There are many reasons for this. Using plain text makes that documentation written 40 years ago can still be read without problems. Furthermore, making it hard to create images forces the authors to write clear documentation. Also, there are programmers/admins that are visual impaired, or even blind. Translating plain text to sound or Braille is a problem solved long time ago. Translating images to sound or Braille is an open problem.
BTW, my posting contained far less than a thousand words. Can you replace my posting with an image that tells the same message? (Disallowing images that just contain the words of my posting). Just because it may take a 1000 words to describe an image doesn't mean any 1000 word message can be told with an image.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
