TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: When is it too much information? From:Ryan Young <ryangyoung -at- gmail -dot- com> To:"Combs, Richard" <richard -dot- combs -at- polycom -dot- com> Date:Tue, 19 Feb 2013 10:13:15 -0800
Right, thank you Richard for the definition.
The purpose of the "Deprecated" section is to let users know what's not
there anymore, which would be ideal for the situation described in the
original post. Then, if the setting moved to a different part of the UI,
that could be described in the "changed features" section. At least, that's
how I think it's supposed to work in an ideal world. Reading through some
older docs, I noticed that those things get muddled. Plus, I suppose, a
user needs to be very familiar with the structure of the release notes for
the structure to really work as intended.
On Tue, Feb 19, 2013 at 9:54 AM, Combs, Richard
<richard -dot- combs -at- polycom -dot- com>wrote:
> Anne Robotti wrote:
>
> > Deprecated? I don't think that word means what they think it means,
> > unless it's a section about features the users complain about!
>
> It has a somewhat different meaning in the software world than in general
> usage. Here's the definition from the Free Online Dictionary of Computing (
> foldoc.org):
>
> "Said of a program or feature that is considered obsolescent and in the
> process of being phased out, usually in favour of a specified replacement.
> Deprecated features can, unfortunately, linger on for many years. This term
> appears with distressing frequency in standards documents when the
> committees writing the documents realise that large amounts of extant (and
> presumably happily working) code depend on the feature(s) that have passed
> out of favour."
>
>
> Richard G. Combs
> Senior Technical Writer
> Polycom, Inc.
> richardDOTcombs AT polycomDOTcom
> 303-223-5111
> ------
> rgcombs AT gmailDOTcom
> 303-903-6372
> ------
>
>
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips
> for creating EPUB, the file format used for e-readers, tablets,
> smartphones, and more.
>
> Learn more: http://bit.ly/12LyN2z
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as ryangyoung -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.
