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

@marcoscaceres 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|,

oh, good point... I'm kinda regretting the way I ended specifying passing in the output map :( That's a very "gecko" thing to do, and I should really switch all these back to returning a parser map... anyway, let's do "map" for now, and then we can fix all of them later. 

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

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