Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-EDITORS] Hyphenating compound terms



--- This message came from the IEEE 802.11 Editors' Reflector ---
Hi Mark,

For framemaker, we have the option to use a standard dash, an en-dash, and an em-dash.  

I agree with your statement that it is both easier for us all, and looks more correct stylistically, if we treat the en-dash recommendations as a regular dash (hyphen) in our documents.  If the Editors decide on this update, then I need to replace all standard dash with en-dash for "non"!!

Regards,
Edward


On Fri, Mar 4, 2022 at 10:25 AM Mark Hamilton <mark.hamilton2152@xxxxxxxxx> wrote:
--- This message came from the IEEE 802.11 Editors' Reflector ---

Thanks for this, Robert.

 

One very minor nit.  I do see/agree with the Chicago Manual’s use of en-dash in some situations.  But, I’ll note that our tools generally only can do a standard dash or an em-dash.  I find the resulting em-dash (not en-dash) in the examples you have below very strange looking, personally.  I think it is both easier for us all, and looks more correct stylistically, if we treat the en-dash recommendations as a regular dash (hyphen) in our documents.

 

My two cents.

 

Mark

 

From: *** IEEE stds-802-11-editors List *** <STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx> On Behalf Of Stacey, Robert
Sent: Friday, February 25, 2022 12:53 PM
To: STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-EDITORS] Hyphenating compound terms

 

--- This message came from the IEEE 802.11 Editors' Reflector ---

Hello Editors,

 

In REVme there is a discussion around the hyphenation of “access point” when it is prefixed with “non”, i.e., is it “non-access-point” or “non-access point”. See Emily’s email copied below.

 

I dug into this a bit and I suggest we defer to the Chicago Manual of Style on this topic. This will be up for discussion at the Editors meeting during the March session.

 

If we do go this route I suggest we add the following to the hyphenation section of our style manual:

 

----

Follow the Chicago Manual of Style for use of the hyphen with a prefix; a hyphen should be used with a prefix in the following cases:

 

•            Before a capitalized word, abbreviation or a numeral, such a sub-AP, pre-1950;

•            Before a compound term, such as non-self-sustaining, non–access point (see below for en-dash vs dash);

•            To separate two i’s, two a’s, and other combinations of letters or syllables that might cause misreading, such as anti-intellectual, extra-alkaline, pro-life;

•            To separate the repeated terms in a double prefix, such as sub-subentry;

•            When a prefix or combining form stands alone, such as over- and underused, macro- and microeconomics.

 

Note that when the hyphen is used before an open compound term, the hyphen is an en-dash (e.g., non–access point). This provides a visual clue that the prefix applies to the whole compound and not just the first word. When the hyphen is before a hyphenated compound, then a regular dash is used (e.g., non-self-sustaining).

 

Further note that this rule means we do not hyphenate a compound term that is not normally hyphenated when adding the prefix.

----

 

Emily, this may mean revisiting some of the following uses (although we could do that through the comment process):

non-quality-of-service

non-very high throughput

non-high-throughput

non-40-MHz-capable

nonaggregate medium access control (MAC) protocol data unit (non-A-MPDU) frame

nonbandwidth signaling transmitter address

nonbufferable medium access control (MAC) management protocol data unit (MMPDU)

nonconcealed groupcast with retries (GCR) frame

nonextended rate physical layer (non-ERP)

nongroupcast with retries (non-GCR)

nongroupcast with retries service period (non-GCR-SP)

non-quality-of-service management frame (non-QMF)

non-space-time-block-coding (non-STBC) frame

non-traffic indication map (non-TIM) mode

non-general link

 

-Robert

 

 

On Tue, Feb 22, 2022 at 3:03 PM Qi, Emily H <emily.h.qi@xxxxxxxxx> wrote:

Hello Robert and Edward,

 

I would like to get your inputs on CID 1295. See below.

 

I found 23 instances in 3.2. They are in the context of "non-access-point (non-AP)" .

However, if the hyphen between “access” and “point” is removed, "non-access-point (non-AP)" will become ""non-access point (non-AP)". It looks odd to me.

 

My personal preference is to keep it as it is.

 

Any thought?

 

Regards,

Emily

 

omments

Selected

CID

Page

Clause

Resn Status

Comment

Proposed Change

Resolution

Owning Ad-hoc

0

1295

3.2

It is a comment resulting from a recent discussion on a specific CID in TGbe. No hyphen is needed for "access point".

Delete hyphen in all appearances of "access-point: in subclause 3.2.

ED1

 


To unsubscribe from the STDS-802-11-EDITORS list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS&A=1


To unsubscribe from the STDS-802-11-EDITORS list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS&A=1


To unsubscribe from the STDS-802-11-EDITORS list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS&A=1