l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jul 22 02:09

The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox] [OT] ISO's vs ISOs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox] [OT] ISO's vs ISOs

On Mon, 22 Jul 2002, Micah Cowan wrote:

> Peter Jay Salzman writes:
>  > begin Henry House <hajhouse@houseag.com> 
>  > > On Sun, Jul 21, 2002 at 11:08:52PM -0700, Peter Jay Salzman wrote:
>  > > > consider the following two sentences:
>  > > > 
>  > > >    A) Getting Debian ISO's has always been a painful experience.
>  > > >    B) Getting Debian ISOs has always been a painful experience.
>  > > > 
>  > > > sentence B seems more correct, but to my eyes, sentence A looks more
>  > > > pleasing; it just looks better with the apostrophe.
>  > > 
>  > > A is a deplorable modern degeneration. B is the correct choice according to
>  > > one style guide, and my personal preference as well. The reader can tell that
>  > > the ess is not part of the acronym by its small case.
>  >  
>  > not good enough.  there are acronyms that use both upper and lower case.
>  > particularly, medical acronyms for chemical names use both upper and
>  > lower case.
>  > 
>  > not all acronyms use all uppercase.  what would you do to make the
>  > sentence unambiguous in that case?

So you would like to write "A bunch of Heliums" as "A bunch of He's" and
suggest that this is somehow clear? Assuming a sentence could be
constructed in which a plural of such an abbreviation made sense, I can't
imagine how adding an apostrophe will make it clearer, given the rules of

> Most of the time (in the case of software naming conventions), those
> acronyms aren't true acronyms, but are a bastardization of the process
> ("borrowing" letters which are not initials). But there's not much to
> do about that.
> Your specific example, though, is a clear reason to use apostrophes,
> at least in those situations. Unless there's another way to
> typographically disambiguate them.

I disagree that it is a clear reason to use apostrophes. It is a clear
reason to reconstruct your sentence to be more clear, most likely by
removing abbreviations.


Here is a reference for the use of apostrophes in technical communication,
though I don't know that it carries any particular weight for anyone here.


Jeff Newmiller                        The     .....       .....  Go Live...
DCN:<jdnewmil@dcn.davis.ca.us>        Basics: ##.#.       ##.#.  Live Go...
                                      Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/Batteries            O.O#.       #.O#.  with
/Software/Embedded Controllers)               .OO#.       .OO#.  rocks...2k

vox mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!