i hesitate to get involved in this kind of thing, but i want to point out that the post in question does not just contain "accurate, factual data" -- it contains an imperitive ("be sure to...") which makes it seem as if it is everyone who buys the camel's responsibility to tell ora about problems in their books. while i personally agree that one should report errata, i do not in any way feel that one must do so; and commands of any form often seem harsh over electronic media, since tone of voice is absent. it would perhaps be more acceptable to some people to word it as "ORA actually appreciates reports of typos, so that they can be fixed in later revisions; they can be reported to..."
on the one hand, i agree that voting based on personality, rather than content, is poor form. on the other, i am reluctant to say that perceived tone is not at all content or the poster's responsibility.
-
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.
|