Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I'm going to agree with ysth's itub's comment: the node title "program line" was terrible; indeed I feel it fit into sauoq's category of "downright, unarguably terrible", as it was both too generic and too non-descriptive. The title "program line" did not, even vaguely, describe the question. The replacement title was better.

I also tend to think that supersearch should (if it already isn't) be "fuzzy" enough so that common misspellings of common words (such as occurrence) should all match; my bete noire is affect|effect, which I never seem to get right. Other people have other spelling blind spots (in one company I used to work for the accepted spelling of mnemonic was pneumonic; I actually had the correct spelling flagged by one of my supervisors). There are also spelling differences by region and dialect, so using supersearch to find "Syntax colorizing tools for Perl" should (and probably does; I've only used supersearch a few times) find the large node originating in Australia about "Syntax colourising tools for Perl".

One category of node title change I would add is that node titles in the instant messager version of English should be re-titled.

Is there an English to IM translator out their? Who is up to writing Lingua::English::IM?

emc


In reply to Re: Consider this: What makes a good node title? by swampyankee
in thread Consider this: What makes a good node title? by sauoq

Title:
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 How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (3)
As of 2024-03-28 15:40 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found