cplusplus / cplusplus/draft

\placeholder or \placeholdernc?

Open
#3,135 5 comments 0 reactions 1 assignee View on GitHub

@jensmaurer is already working on this.

Since Aug 6, 2019.

Dominant language
TeX
Stars
221
Forks
813
Avg merge
16h 4m
Merged PRs (30d)
36

Description

I've seen both \placeholder and \placeholdernc used within tcode/codeblock contexts throughout the spec. The nc form should be used to turn off italic correction in places where it "looks bad", but it's not clear what constitutes such a place. This should be clarified in our guidelines with examples of when to use each, and we should do a sweep of the Latex sources to fix any incorrect uses.

In #3056, @zygoloid provides some hints as to when to use which:

Please don't blindly change \placeholder to \placeholdernc. The latter is a surgical tool for fixing cases of bad kerning due to italics corrections, and should be used sparingly only where there is actual bad kerning. Usually the italics correction is what we want; the bounding box for italicized text is wider due to the right overhang, and it so we want to create a little extra space.

I've found that \placeholdernc improves the presentation immediately before a period or a comma (where there is no higher text for the italics to get uncomfortably close to). So let's take that as rough guidance for now: use \placeholdernc before a teletype period or comma, where there would otherwise be an unsightly amount of horizontal space.

Looking through a few more examples, \placeholdernc before a left paren also seems more pleasant to my eye, but before a left angle bracket I prefer including the italic correction.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.