Re: [w3c/manifest] Should dir and lang apply to name/description of app shortcuts? (#872)

> Yes, I think that would be useful. As an example, the [Publication Manifest](https://w3c.github.io/pub-manifest/#manifest-lang-dir) provides the ability to set both these concepts globally as well as on individual items.

Good precedent. I suppose we should not let the perfect (per-string settings) be the enemy of the good (global settings).

> For example, it can be used for selection of appropriate fonts (since the same code point can be rendered differently in different languages) or pronunciations (like screen readers). If we don't have consensus on how `lang` should be implemented now, we can mark the behavior as UA-dependent and add more normative text when the UA behaviors converge in the future.

I see. (I assume the "appropriate fonts" thing refers to [Han unification](https://en.wikipedia.org/wiki/Han_unification) for CJK languages.) I think we need a bit more normative text around `lang` for it to be useful. At the moment, it is too closely related to text directionality. For example, `lang` is specified as applying to "directionality-capable members". Perhaps we need to rename "directionality-capable members" to "user-facing string members", to reflect their role more accurately: these concerns (text direction, font choice, screen readers) are applicable to all strings that are intended to be displayed to the end user, as opposed to strings like URLs, IDs, enums, and colors.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/872#issuecomment-633363805