NAD: Comment provides no examples, and a search through the standard does not find any. Some paragraphs have an indent after an example or note; this is fixed in the working draft but will not be fixed for C++14, and is not a hanging indent.

We need to fix the indented paragraphs after codes. The affected
paragraphs are difficult to read. Compare with C++98 and C++03 documents.

On Thu, Aug 21, 2014 at 6:04 PM, Richard Smith notifications@github.com
wrote:

NAD: Comment provides no examples, and a search through the standard does
not find any. Some paragraphs have an indent after an example or note; this
is fixed in the working draft but will not be fixed for C++14, and is not a
hanging indent.

—
Reply to this email directly or view it on GitHub
#377 (comment).

Yes. This is already fixed in head, we need to decide whether to take this change into the C++14 IS. My initial position is that I'm opposed:

• we've lived with this in our drafts for a couple of years
• it's a disruptive change to the standard's document, and introduces risk of major formatting problems
• we do not have sufficient time to gain confidence that no regressions have been introduced

Stefanus also indicated that he doesn't see this as sufficiently pressing to be worth fixing for C++14.

On Sun, Aug 24, 2014 at 10:15 PM, Richard Smith notifications@github.com
wrote:

Yes. This is already fixed in head, we need to decide whether to take this
change into the C++14 IS.

Yes, that is the suggestion: to make the correction in C++14 IS.

My initial position is that I'm opposed:

-- we've lived with this in our drafts for a couple of years

Drafts are generally to be incomplet, incorrekt, and, yes, ghastly
formatted :-)

-- it's a disruptive change to the standard's document, and introduces
risk of major formatting problems

Hmm, removing the misplaced indentation should be a matter of inserting
\noindent.

-- we do not have sufficient time to gain confidence that no regressions
have been introduced

Stefanus also indicated that he doesn't see this as sufficiently pressing
to be worth fixing for C++14.

It is a serious disruption from previous published IS and really an
impediment to readability.

—
Reply to this email directly or view it on GitHub
#377 (comment).