Skip to content

Editorial: Replace ASCII quotes with typographic quotes as appropriate#3861

Open
gibson042 wants to merge 2 commits into
tc39:mainfrom
gibson042:gh-3860-typographic-quotes
Open

Editorial: Replace ASCII quotes with typographic quotes as appropriate#3861
gibson042 wants to merge 2 commits into
tc39:mainfrom
gibson042:gh-3860-typographic-quotes

Conversation

@gibson042
Copy link
Copy Markdown
Member

Stacked on #3859, because I noticed the issue while fixing #3858.

Fixes #3860

@gibson042 gibson042 added editorial change editor call to be discussed in the next editor call markup things that change the spec rendering, but not the contents establishes editorial conventions labels May 15, 2026
@github-actions
Copy link
Copy Markdown

The rendered spec preview for this PR is available as a single page at https://tc39.es/ecma262/pr/3861 and as multiple pages at https://tc39.es/ecma262/pr/3861/multipage .

Comment thread spec.html
Comment on lines -3231 to 3232
<li>[[Type]] = ~normal~, [[Target]] = ~empty~, and [[Value]] = a value of the "normal return type" shown below for that internal method, or</li>
<li>[[Type]] = ~normal~, [[Target]] = ~empty~, and [[Value]] = a value of the normal return type shown below for that internal method, or</li>
<li>[[Type]] = ~throw~, [[Target]] = ~empty~, and [[Value]] = any ECMAScript language value.</li>
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quotation changes aside, the equals signs in this text don't look right to me. I think some refactoring would improve it.

@michaelficarra michaelficarra force-pushed the gh-3860-typographic-quotes branch from c77ec10 to 77d00d6 Compare May 16, 2026 16:15
Copy link
Copy Markdown
Member

@michaelficarra michaelficarra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please drop the first commit.

gibson042 added 2 commits May 17, 2026 00:23
When _referencing_ `?` and `!` (as opposed to _using_ them), enclose
them in typographic quotes rather than backticks. Using quotes aligns
with editorial conventions (albeit inconsistently applied), while using
backticks makes them render as if they were
[grammar terminal symbols](https://tc39.es/ecma262/multipage/notational-conventions.html#sec-terminal-symbols).
@gibson042 gibson042 force-pushed the gh-3860-typographic-quotes branch from 77d00d6 to d6c9562 Compare May 17, 2026 04:23
@gibson042
Copy link
Copy Markdown
Member Author

Please drop the first commit.

Done.

@gibson042 gibson042 requested a review from michaelficarra May 17, 2026 16:52
Copy link
Copy Markdown
Member

@linusg linusg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me with a preference for automated linting if feasible - easy to forget and not easy to catch depending on the font.

Copy link
Copy Markdown
Member

@michaelficarra michaelficarra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's some quotes that can just be dropped, but this is an improvement.

@michaelficarra michaelficarra removed the editor call to be discussed in the next editor call label May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

editorial change establishes editorial conventions markup things that change the spec rendering, but not the contents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Spec prose is inconsistent about using ASCII vs. typographic quotes

3 participants