Yes, the cheat sheet will reflect what is shown by my client. But I don't think that's a reason to abort the creation of such a cheat sheet for the benefit of newcomers, or experienced monks who care to "use" it.
True, we can never judge how text is rendered for others. All I need to know is that it looks good enough for me, and that it'll look "more or less" the same for others (if it doesn't, who cares? I've done my best).
As a newcomer, I can't even get it to look good enough for myself! let alone others... Do you see where I'm coming from now? :)
By the way, how do you "indent and italicize" to show that you're replying-to, like you did with my "All the more ...
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.