The other day, I found a great scenario of what you're describing. A lead writer at Adobe doesn't suppress the limitations of the product he documents. He handles it in a really classy way on his blog. In his blog he has more freedom to write this way, it seems. For the example, check out http://blogs.adobe.com/
indesignd...design_cs4.html and see his lead sentences: "Whenever people ask if they can create endnotes in InDesign, I have to explain the same sad story. No, InDesign has footnotes not endnotes, but you can download a plug-in . . ."
His judgment call was great, and I believe the whole scenario is one we'll see more and more of if writers are given the correct outlets to offer these messages outside of the "vetted" documentation. The wonderful part of the story is that he weaved in information from support forums and then a user posted a script that automated the procedure he describes in the blog entry. I wrote up the "information trail" in a blog entry on my blog at http://justwriteclick.com/2009/0...ue-the-content/
if you want to read the whole story - I think it's a great example!
Judging from old TV crime series, the UK newspapers have often kept quiet about kidnappings and ransoms. Keeping it out of Wikipedia is a new development. I guess editors would argue that reporting a kidnapping could be seen as much as manipulation as not reporting it.
Commenting by HaloScan
