- From: Fuqiao Xue <notifications@github.com>
- Date: Sun, 24 May 2020 20:24:25 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 25 May 2020 03:24:38 UTC
> I have never liked them, because it's weird to be forced to set the same directionality and language on all of the strings, rather than on a per-string basis. 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. > I'm not sure what `lang` is even for. It says "knowing the language can also help with directionality" but there's nothing normative about how it is to be used (for example, it doesn't say that "base direction" is `dir` but falls back to the direction implied by `lang`, if `dir` is omitted... `lang` simply has no normative meaning in this spec). 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. -- 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-633357097
Received on Monday, 25 May 2020 03:24:38 UTC