Your post happens to demonstrate one formatting tip that seems
to make a difference on my linux-based Netscape 4.78 browser:
Whenever I view a post with a <UL> or <OL>
construct, and the close tag for the construct is
followed immediately by text (without a <P> tag in
between), the last list element and the first line of text
overlap on the same line of the display, and are not
readable -- I need to view the page source to see what was
actually written. (Oddly when I reply to such
a node, the same markup displays correctly, no problem.)
In any case, I have gotten into the habit, when using the
list elements in my own posts, of always putting a <P>
right after the end of each list -- this always assures a
good display.
-
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.
|