In email from Daniel Krugler:

Dear editors of the working draft!

I would like to ask whether the following editorial improvement could
be realized, when (In case of acceptance),

http://wiki.edg.com/pub/Wg21kona2017/StrawPolls/p0604r0.html

would be transferred into the working draft:

I noticed in the past, that in the pdf output of the working draft, a
font change between italics and non-italics (such as in
"INVOKE(" between 'INVOKE' and '(') there often seems to
be an additional space character introduced. This makes is hard to
search reliably for the character sequence 'INVOKE(', for example.
Now, for this sequence there is not often a use-case. But P0604R0
introduces a new "overload" of INVOKE, INVOKE<something>. When my
paper was discussed, people were concerned that this overload will be
hard to search in the working draft when looking for 'INVOKE<'. And
given the above problem, I tend to agree. Therefore I would like to
ask, whether it would be possible for your and hopefully lead to a
more reliable search success, when you editors could rewrite the
currently term in partial html

INVOKE<R> (in html: <i>INVOKE</i>&lt;R&gt;)

into the alternative partial html form

INVOKE<R> (in html: <i>INVOKE&lt;</i>R<i>&gt;</i>)

?

This change wouldn't change the semantic meaning, because neither
INVOKE nor INVOKE are C++ language constructs but plain symbolic
definitions and in fact it would presumably slightly improve the
clarity that this is just such a construction when it would be spelled
as

INVOKE<R> (in html: <i>INVOKE&lt;</i>R<i>&gt;</i>)

I should say that it is just my guess that this rewrite would also
solve the font-change-additional-space character problem, but maybe
you can give a better explanation for this artifact.

Thanks very much,

• Daniel