Re: [w3c/manifest] Add members for localization (PR #1101)

@christianliebel commented on this pull request.



> +              require specific direction settings if the manifest's default
+              direction is left-to-right, and vice versa.
+            </p>
+            <p>
+              To support multilingual content and ensure proper display and
+              accessibility, it is possible to specify a different [=language
+              tag=] for a [=localized value=]. This is needed for situations
+              where a term or text must be presented in a language different
+              from the user's set language. For example, this helps ensure that
+              an application name is correctly pronounced by assistive
+              technology, even if it is in a foreign language.
+            </p>
+          </aside>
+          <p>
+            To <dfn>process a `*_localized` text member</dfn>, given [=ordered
+            map=] |json:ordered map|, [=ordered map=] |map:ordered map|,

I tried to be consistent with the other algos in the spec that use “map” currently. If we change this, should we change all uses of “map”?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1101#discussion_r1671676820
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1101/review/2168123838@github.com>