this is why I'd like to see the <l/> we're supposed to get one of these days
I personally believe you left me a little bit behind now: is <l/> a proposal of yours or an existing tag and if so, then in which markup language?
To put the matter in other terms, I would like to make it clear that I can happily and daily "survive" in the realms of *ML editing, but I'm far from being an expert in any of them, and really only use a well defined subset of all the available tags - incidentally and on a totally OT basis, the little I have seen of HTML 5 already makes me cherish it...
To bring the discussion back in topic wrt not only PerlMonks but even Perl itself, I wonder whether considerations of the kind of the one you're doing are being taken into account in the development of Perl 6's new POD and in particular if they make sense at all there, given that it's supposed to be a lightweight markup language - but even more so: if few concepts have to be supported in such a restricted environment, it's important that they are thought out very well.
-
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.
|
