Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[std] Use \Fundescx to avoid awkward mid-sentence colons. #4772

Closed
wants to merge 1 commit into from

Conversation

Eelis
Copy link
Contributor

@Eelis Eelis commented Jul 25, 2021

image

There is precedent here, for example:

draft/source/lib-intro.tex

Lines 374 to 378 in b4e36f7

Whenever the \Fundescx{Effects} element specifies that the semantics of some function
\tcode{F} are \term{Equivalent to} some code sequence, then the various elements are
interpreted as follows.
If \tcode{F}'s semantics specifies any \Fundescx{Constraints} or \Fundescx{Mandates} elements,
then those requirements are logically imposed prior to the \term{equivalent-to} semantics.

@jensmaurer
Copy link
Member

If we do this, I'd prefer new LaTeX macros like \requiresx or so, instead of introducing the chance of misspelling those items. Oh, and the definition of \requires should then use \requiresx, of course.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Jul 25, 2021
@Eelis
Copy link
Contributor Author

Eelis commented Jul 25, 2021

Amended as suggested.

@tkoeppe
Copy link
Contributor

tkoeppe commented Sep 24, 2021

I'm not entirely convinced that a change is needed here at all (the status quo has a certain appeal even), but if you do want to pursue this, two questions:

  1. Can we have starred versions, like \effects*, to not have the colon?
  2. Can we generate all the macros more compactly, say by defining a "meta macro" in TeX that emits multiple macros? The goal would be to only have to say each base name once, and have all the derived macros generated automatically.

@tkoeppe tkoeppe self-assigned this Oct 20, 2021
@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 19, 2021

I'm tempted to just live with the status quo. Please reopen if you feel strongly. At the very least we would want a system that does not require us to state every element twice in macros.tex.

Also, @jwakely, do you have any opinions? We'd like LWG approval for this change, too.

@tkoeppe tkoeppe closed this Nov 19, 2021
@jwakely
Copy link
Member

jwakely commented Nov 19, 2021

I'm happy with the status quo.

@Eelis
Copy link
Contributor Author

Eelis commented Dec 1, 2021

the status quo has a certain appeal even

I suspect an editor of any professional publication would be fired on the spot if they let through an error as egregious as having colons in sentences without those colons actually serving as colons but instead serving as some kind of implicitly quoted colons because they appear unquoted elsewhere. But that's just me and I don't feel strongly about having the document look like amateur hour (it does so regardless, after all), so it's fine with me. :)

@Eelis Eelis deleted the fundescfixes branch December 1, 2021 10:40
@jensmaurer
Copy link
Member

@tkoeppe, I guess that counts as a strong opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision-required A decision of the editorial group (or the Project Editor) is required.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants