Skip to content

A few proposed tweaks to syntax.md. #745

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Mar 25, 2024
Merged

A few proposed tweaks to syntax.md. #745

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a03d2e
A few proposed tweaks to syntax.md.
bhaible Mar 25, 2024
0e3ffdb
Subtle wording regarding whitespace around a reserved-body.
bhaible Mar 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions spec/syntax.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,7 +347,7 @@ of the _pattern_ to use for formatting.
This allows the form or content of a _message_ to vary based on values
determined at runtime.

A _matcher_ consists of the keyword `match` followed by at least one _selector_
A _matcher_ consists of the keyword `.match` followed by at least one _selector_
and at least one _variant_.

When the _matcher_ is processed, the result will be a single _pattern_ that serves
Expand Down Expand Up @@ -637,17 +637,19 @@ A **_<dfn>reserved annotation</dfn>_** is an _annotation_ whose syntax is reserv
for future standardization.

A _reserved annotation_ starts with a reserved character.
A _reserved annotation_ MAY be empty or contain arbitrary text after its first character.
The remaining part of a _reserved annotation_, called a _reserved body_,
MAY be empty or contain arbitrary text that starts and ends with
a non-whitespace character.

This allows maximum flexibility in future standardization,
as future definitions MAY define additional semantics and constraints
on the contents of these _annotations_.
A _reserved annotation_ does not include trailing whitespace.

Implementations MUST NOT assign meaning or semantics to
an _annotation_ starting with `reserved-start`:
an _annotation_ starting with `reserved-annotation-start`:
these are reserved for future standardization.
Implementations MUST NOT remove or alter the contents of a _reserved annotation_.
Implementations MUST trim whitespace around a _reserved body_,
but MUST NOT remove or alter the contents of a _reserved body_.

While a reserved sequence is technically "well-formed",
unrecognized _reserved-annotations_ or _private-use-annotations_ have no meaning.
Expand Down