Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A A tricky serial semi-colon

(I'm answering this from a point-of-view of readability. If your corporate communications are subject to any internal style sheets or style guide such as AP or Chicago - since you have a policy on ...

posted 12y ago by Neil‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T02:18:18Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/5430
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T02:18:18Z (about 5 years ago)
(I'm answering this from a point-of-view of readability. If your corporate communications are subject to any internal style sheets or style guide such as AP or Chicago - since you have a policy on the serial comma, I'm inclined to think they are - please also consult those. If this does get migrated to English, you'll doubtless get all kinds of more technical answers there.)

As you obviously know, the serial comma exists to enhance readability. You've already outlined its use above, so I won't repeat that. The serial _semicolon_ - even though I'm familiar with the semicolon's use in the way you describe, that's a new term for me!

Phrases with commas separated by semicolons like this, while technically correct, can be ponderous and difficult to parse. Many readers will _skim_ this text, not read it. This is email/brochure copy, not a novel, so I would, rather, suggest formatting this text as a bulleted list for maximum utility. The reader will see it and be able to decode the format at a glance.

> **Speakers at tomorrow's conference include:**
> 
> - James T. Smith, vice president of widgets at WidgetCo.
> - Mary Holmes, chief foo officer at FoobRUs
> - Sheldon DeVane, head of global placeholding at RiMelioraDies Inc., and
> - Lisa Catera, chief lending officer at Plugitin Motors

However, sometimes a bulleted list isn't an option (for layout or other reasons). In that case, my next suggestion would be to rewrite the sentence like this:

> Speakers at tomorrow's conference include WidgetCo's vice president James T. Smith, FoobRUs's chief foo officer Mary Holmes, RiMelioraDies Inc's head of global placeholding Sheldon DeVane, and Plugitin Motors's chief lending officer Lisa Catera.

I agree that the semicolon does interrupt the flow of the text. If you can, I'd replace the longer titles with "executive" or something similar. Shorter is better. (Perhaps you could include profiles of the speakers elsewhere in the document with more complete titles?)

Finally, if none of this is possible, I suggest you use your last attempt at this, the one starting with "Speakers at tomorrow's conference include". Putting this information at the end of the paragraph requires that readers read through a lot of names and titles to get to the point of the paragraph. Putting it at the beginning of the paragraph at least tells them what the paragraph is before they proceed, and the can decide to read or skim based on what information they need.

#1: Imported from external source by user avatar System‭ · 2012-04-12T17:55:23Z (over 12 years ago)
Original score: 3