Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Re^2: Additions to Approved HTML

by kcott (Bishop)
on Jun 29, 2015 at 17:49 UTC ( #1132502=note: print w/replies, xml ) Need Help??


in reply to Re: Additions to Approved HTML
in thread Additions to Approved HTML

Thanks for registering your general agreement, ww. ++

When considering the "<code uni="1">" and "<code uni>" forms, I chose the latter for reasons of brevity and, therefore, esae of use. The W3C Standards (for HTML4) do include examples of this form; for instance, checked and disabled. Your preference for "<code uni="1">" is noted and will be taken into account with other feedback I receive.

Referring back to ambrus' post (Re^4: Approved PM markup?), you'll see that embedded CSS (via the style element or style attributes) will not be allowed, so I won't be proposing "<span style=..." at all. Similarly, from the same post, "<span class=..." within code tags, would allow syntax-highlighting, so that's off the table as well.

Regarding br, that's a modification so I won't be including it in the proposal. I believe if I keep the proposal tight, i.e. just to additions, I'm more likely to get somewhere with this, than I would if I allowed feature-creep. Having said that, should you wish to make a separate proposal, for instance, "allow br inside p blocks but continue to discourage its use as an alternative to using p blocks", I would certainly support that.

-- Ken

Replies are listed 'Best First'.
Re^3: Additions to Approved HTML
by ww (Archbishop) on Jun 30, 2015 at 17:45 UTC

    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.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1132502]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (2)
As of 2021-10-17 04:43 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My first memorable Perl project was:







    Results (71 votes). Check out past polls.

    Notices?