Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

OK, re-read Re^4: Approved PM markup? but should not have needed to had I read more carefully before.

However, just as we implemented non-standard tags -- <code> etc -- skilled individuals could, I suspect, implement equivalents for a limited variety of style-attribute-equivalents -- .red, .green. etc. Creating a few of those would go a long way, IMO, to making it possible to highlight important subject matter in ways that would enhance communication other than <>;font>; <b>; <em>; <big> etc.

As things stand now, explaining some issues appearing in CODE requires lengthy notes pointing out that problem x at line such-and-such in your original creates problems at... at a remove from the problem (i.e., in the narrative rather than the code) or requires an extended comment in the code section, interrupting the flow.

My intent re span is NOT TO PROVIDE SYNTAX HIGHLIGHTING but rather to provide non-standard tag -- say <note> maybe -- as a means to create a visibly distinct rendering for comments inserted inside code tags without the limitations of using the hash_sign or pod markup.

As to <br>, you invited general comments. My thoughts on that were clearly an aside for the community reading your (++ed) thoughts.

In reply to Re^3: Additions to Approved HTML by ww
in thread Additions to Approved HTML by kcott

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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 or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (8)
As of 2021-12-09 09:45 GMT
Find Nodes?
    Voting Booth?
    R or B?

    Results (36 votes). Check out past polls.