- From: Google <sysbot+gh@w3.org>
- Date: Wed, 20 Sep 2017 21:27:29 +0000
- To: public-webscreens@w3.org
> On the other hand, I wonder if the MESSAGE_LOCALE field in Presentation Application Message would be useful or not. Unless any method or parameter to specify a locale of each message is not exposed to web applications, the field will eventually be set to the same string as specified in Presentation Initiation Request and will not vary until the presentation would be terminated Good point. I remember we discussed passing locale information with application messages, and deciding on leaving it up to the application, as it knows best which messages need a locale and what that locale is. In the future, we could add an API like `send(<body>, <locale>)` to allow applications to pass a locale with a string to capture this pattern. For now, I'll remove `MESSAGE_LOCALE` since I don't think either end has a good way to fill it. > By the way, I suppose that each locale field could have variable length. In most cases, a locale string is very short like en-US, zh-CN, zh-TW, ko, ja, etc. The BCP-47 spec doesn't seem to limit the length because of arbitrary variant strings that can be appended to the two letter codes. 64 characters captured all examples from the spec, but I didn't research this deeply. We could restrict to a subset of BCP-47 if we want to ensure shorter codes. Maybe the i18n WG would have some advice for us on this. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/pull/53#issuecomment-330986110 using your GitHub account
Received on Wednesday, 20 September 2017 21:27:22 UTC