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: Functionalities vs Functionality From:Jim Purcell <jimpur -at- MICROSOFT -dot- COM> Date:Fri, 28 Feb 1997 11:05:48 -0800
Ana Maria Gallo writes:
> >As Saglieri might have said: it has too many syllables. And I agree.
> >use functionality or functionalities when function is all that is
> This solution is perfectly serviceable, as long as you're writing for
> end users. For a programming audience, "function" has a specialized
> meaning, which is why the back-formation "functionality" got coined in
> the first place.
> "Functionality" is collective--a program's functionality comprises all
> its functions and features. There's never a need for a plural.
> Jim Purcell
> jimpur -at- microsoft -dot- com
> My opinions, not Microsoft's