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.
Yves wrote:
>Thanks for that. Raj's request sounds like the "Strength of the weak"
argument
that Lyotard talks about. :-)>
Yves:
Thanks for introducing me to Lyotard and the "Strength of the weak"
argument. Sounds interesting. :)
The sole aim of my request concerning the style guide was to arrive at a
definite conclusion about the usage of "and/or" in technical documentation.
I thought it would be useful to find out whether we have any other logical
perspective in support of "and/or".
Technical writing is a dynamic field and is evolving constantly. Guess we do
not have any option but to dive deep before forming an opinion.
Regards,
Raj
On 6/26/07, Yves JEAUROND <jingting -at- rogers -dot- com> wrote:
>
> Mark:
>
> Thanks for that. Raj's request sounds like the "Strength of the weak"
> argument
> that Lyotard talks about. :-)
>
> In a nutshell: (A) if a small man is accused of beating up a dozen
> large fellows, he could plead legitimately that, not having the strength
> to do so, he thus could not have. Thus an accusation is shown and made
> to be implausible.
> (French: "invraisemblable"). This is the (rhetorical) strength of a weaker
> man.
>
> However (B) if a gang of men are accused of beating up one man,
> and they plead that, since they had the means, and appearances were
> against them, it would have been foolish to have even contemplated
> assaulting the fellow. And thus, they could not have done it.
> "Error! Aristotle would say. These ruffians are arguing that a plausible
> accusation is implausible." (Lyotard) They are pleading the
> strength of the weak position, from a position of strength.
>
> Which brings me back to "and/or". Finding style guides that support
> good semantics is plausible.
> Are attempts at finding a style guide to support bad semantics
> similar to those ruffians attempting to make the implausible appear
> as plausible, as in (B) above?
>
> Regards,
>
> YJ
>
>
>
> *"Mark L. Levinson" <nosnivel -at- netvision -dot- net -dot- il>* a écrit :
>
> Raj Machhan wrote:
> > It would be a great
> > value addition to this thread if anybody could come up with a style
> > guide that favors that use of "and/or".
>
> I'm not sure any addition to this thread has value
> any more, but here goes:
>
> From _The Handbook of Good English_, by
> Edward D. Johnson:
>
> - quote -
>
> and/or a convenient and compact device--
> it isn't really a word or even a conventional
> compound-- but a graceless one. It has a place
> in legal, commercial, and technical writing, in
> which precision and compactness are more important
> than grace, but even in such writing it is often
> unnecessarily used when _or_ alone would carry
> the meaning. Elsewhere it should be avoided,
> even though avoiding it may require several
> additional words.
>
> - end quote -
>
> In short, as Johnson says elsewhere in the
> same book, "_And/or_ can be effectively used,
> but too often it merely camouflages muddy
> thinking."
>
> ------------------------------------------------
> Mark L. Levinson - nosnivel -at- netvision -dot- net -dot- il
> ------------------------------------------------
> Mark discourses to fellow Israeli techwriters in
> The Why of Style, at http://www.elephant.org.il/
> ------------------------------------------------
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Create HTML or Microsoft Word content and convert to Help file formats or
> printed documentation. Features include support for Windows Vista & 2007
> Microsoft Office, team authoring, plus more.
>http://www.DocToHelp.com/TechwrlList<http://www.doctohelp.com/TechwrlList>
>
> True single source, conditional content, PDF export, modular help.
> Help & Manual is the most powerful authoring tool for technical
> documentation. Boost your productivity! http://www.helpandmanual.com
>
> ---
> You are currently subscribed to TECHWR-L as jingting -at- rogers -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/jingting%40rogers.com
>
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-