Skip to content

spec: INTENT-2 — implementation-neutral language-fallback wording #120

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

Draft
JarbasAl wants to merge 1 commit into
base: dev
Choose a base branch
from
Draft

spec: INTENT-2 — implementation-neutral language-fallback wording #120

Show file tree
Hide file tree
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
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,11 @@ version 2: its `{{ … }}` sequences become substitution points, and its
engine extracts only the slots of the matched template. The prior "every line
MUST declare the same set of slots; use a separate file" rule is dropped for
`.intent` (it still holds for `.dialog`, §4.2).
- Consistency review: §2.2 language-fallback suggestion made
implementation-neutral — a loader MAY fall back to the nearest
available language as measured by any language-tag distance metric
that treats close regional variants as usable matches; the reference
to one particular library and its numeric threshold is removed.

### 1

Expand Down
6 changes: 3 additions & 3 deletions intent-2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,9 +126,9 @@ an override file replaces the corresponding lower-precedence file entirely.

This specification does not mandate behaviour when the requested language has no
directory. A loader **SHOULD** prefer an exact match. As a *suggestion*, a
loader MAY fall back to the nearest available language; the `langcodes` library
provides a `tag_distance()` function for this, and treats a distance below `10`
as a usable regional match. Any such fallback is an **implementation choice**,
loader MAY fall back to the nearest available language, as measured by any
language-tag distance metric that treats close regional variants as usable
matches. Any such fallback is an **implementation choice**,
not a requirement of this specification, because cross-region substitution can
produce wording a user would not expect.

Expand Down