Skip to content
Open
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -234,7 +234,7 @@ A <dfn>language arc</dfn> is a [=tuple=] of two strings, a <dfn for="language ar

<xmp class="language-js">
function a(sourceLanguage, targetLanguage) {
return ai.translator.availability({ sourceLanguage, targetLanguage }):
return Translator.availability({ sourceLanguage, targetLanguage });
}

await a("en", "zh-Hans") === "available";
Expand Down Expand Up @@ -274,7 +274,7 @@ A <dfn>language arc</dfn> is a [=tuple=] of two strings, a <dfn for="language ar

Instead, a typical user agent will either support only one English-to-French language arc (presumably ("`en`", "`fr`")), or it could support multiple non-overlapping English-to-French language arcs, such as ("`en`", "`fr-FR`"), ("`en`", "`fr-CA`"), and ("`en`", "`fr-CH`").

In the latter case, if the web developer requested to create a translator using <code highlight="js">ai.translator.create({ sourceLanguage: "en", targetLanguage: "fr" })</code>, the [$LookupMatchingLocaleByBestFit$] algorithm would choose one of the three possible language arcs to use (presumably ("`en`", "`fr-FR`")).
In the latter case, if the web developer requested to create a translator using <code highlight="js">Translator.create({ sourceLanguage: "en", targetLanguage: "fr" })</code>, the [$LookupMatchingLocaleByBestFit$] algorithm would choose one of the three possible language arcs to use (presumably ("`en`", "`fr-FR`")).
</div>

<div algorithm>
Expand Down