On Thu, Feb 4, 2010 at 3:18 PM, Kent West <we...@acu.edu> wrote: > Why, oh why, don't "professionals" proof-read their material? > > On the first page, in the first paragraph: >> The GNU/Linux systems have reached an important level of maturity, >> allowing to integrate them in almost any kind of work environment, >> from a desktop PC to the *sever* facilities of a big company.
A legitimate issue for publishers. One problem is writers who think spell checking is good enough. Clearly their self-expectations are set too low. Another problem is that it is extremely difficult for a writer to read what he actually wrote as opposed to what he intended to write. Even worse is the problem of what he meant by what he intended to write as opposed to what the reader might think he meant by what he actually wrote. This is why proofreading is a serious, professional (and thus expensive) skill. Multi-platform software coders learn the basics of such parallel, multi-path interpretation when they confront the problem of multiple compilers all of which claim to be standard, but no two of which interpret certain code fragments the same way. -- Lee -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
