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.
> Question: Should the writer point out the "un-PC-ness" -- excuse my
> language -- of either or both of these examples to the development team
> and/or the management?
> Example 1:
> In a "Programmer's Guide" that is to be used by future maintenance
> programmers documenting the database. The database field name is
> "indian_tribe" and the field description is "Indian tribe blah-de-dah".
> Should the writer tell the database guy that the database field name needs
> to be changed because it isn't "Native American"?
That really depends on the purpose of the database field name. If they need
to specify an actual Indian tribe, then I don't see what the problem is.
> Example 2:
> On a "button" in an application used by Field Engineers: "Men/Equipment".
> Should the writer advise the team that the button name should be changed so
> as not to discriminate against women?
Yes, unless you can't think of a better word to replace "men", or unless it
causes undue hardship. I get annoyed when I see references to "men" that
clearly mean "people" (Sometimes I think that the Ten Commandments don't apply
to me, since no-one ever instructed me not to covet my neighbor's husband, and
I have no interest in my neighbor's wife).
Nora
merhar -at- edsvcs -dot- switch -dot- rockwell -dot- com
