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.
Re: Deprecated (was When is it too much information?)
Subject:Re: Deprecated (was When is it too much information?) From:Stuart Burnfield <slb -at- westnet -dot- com -dot- au> To:Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 22 Feb 2013 09:29:13 +0800 (WST)
Lauren <lauren -at- writeco -dot- net> said:
> The term is perfect for documentation read by programmers,
> but users are not likely to understand it.
True. I can just about picture using this term in end-user docs, but it would have to be defined clearly on the spot. For example, in a table showing fields or features supported in different versions of a product, there might be a column or symbol to indicate 'supported but deprecated', but there would have to be a footnote or at the very least a glossary entry explaining what that means.
>From : "Peter Neilson" <neilson -at- windstream -dot- net>
> As I recall, the term "deprecated" has been in use for decades
> in the software-standards business. Here is some research. ..
Great catch or series of catches, Peter. Interesting to see the word used in the modern sense in documents from the 1890s.
Stuart
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
