Skip to content

Address phrasing comment on #647 #674

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 1 commit into from
Feb 21, 2024
Merged

Address phrasing comment on #647 #674

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 5 additions & 3 deletions spec/syntax.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -726,9 +726,11 @@ might not match future requirements or usage.
> that of the overall _message_ locale, or use a namespace that later maps to the final
> mechanism.
> - Avoid specifying options for the purpose of linking placeholders
> (such as to pair opening markup to closing markup)
> or require that such options use an implementation-specific namespace
> while cautioning users that such option might be replaced or unavailable later.
> (such as to pair opening markup to closing markup).
> If such an option is created, the implementer should use an
> implementation-specific namespace.
> Users and implementers are cautioned that such options might be
> replaced with a standard mechanism in a future version.
> - Avoid specifying generic options to communicate with translators and
> translation tooling (i.e. implementation-specific options that apply to all
> functions.
Expand Down