It's not a case of poor spelling, is a case of acronyms and capitalization. "Pearl" would be just plain wrong, and could even imply a completely different language.

When faced with a stack of resumes, it's reasonable to weed out the candidates based on some criteria, even if the approach takes on a Perl vs PERL evaluation. Employers are entitled to use what ever methods they feel meets their needs. If an application doesn't meet the criteria, move on or issue the standard "thanks but no thanks" form letter. Just don't waste the company or the applicants time with condescending "spell it right" crap.

In reply to Re^3: To Perl or not to PERL. by ruzam
in thread To Perl or not to PERL. by jethro

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.