Skip to main content

punctuation - To hyphenate or not?


As a non-native speaker of English and an engineer by training, I always get confused about hyphenation and almost always end up referring to Google every time I need to make that decision.


Does anybody know of a concise, comprehensive style guide to hyphenation that explains this rather complex issue, once and for all?



Answer



Asking for something that is both concise and comprehensive is, unfortunately, contradictory. The Chicago Manual of Style, 14th Edition devotes one full page (5 numbered sections, 6.38-42) to "general principles" of hyphenating compound words, but then also goes on to list a 13-page table of common forms, when to hyphenate them, when not to, and when to make exceptions to other parts of the table.


To summarize the relevant segments for you, though:


6.38: The trend in spelling compound words has been away from the use of hyphens; there seems to be a tendency to spell compounds solid [i.e. unhyphenated] as soon as acceptance warrants their being considered permanent compounds.


6.39: When a temporary compound is used as an adjective before a noun, it is often hyphenated to avoid misleading the reader. (e.g. "a fast sailing ship": is it a "ship that is sailing fast", in which case you should hyphenate it, or "a sailing ship that is fast", in which case you should leave it unhyphenated.)


6.40: Where the compound adjective follows the noun it modifies, there is usually little to no risk of ambiguity or hesitation, and the hyphen may be safely omitted. [There are, of course, exceptions to this, as in "her reply was thought provoking."]


6.41: [contrary to its earlier positions,] The University of Chicago Press now takes the position that the hyphen may be omitted in all cases where there is little or no risk of ambiguity or hesitation.


6.42: There are scores of other rules for spelling compound words, but many of them are all but useless because of the multitude of exceptions. See table 6.1 [that 13-page behemoth of a table mentioned above] for some of the more dependable rules.


Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...