Re: [heycam/webidl] No "Localizable" type (#1025)

@annevk I18N generally recommends that each natural language text field have its own metadata. This allows different fields to have separate values, which is often appropriate.

A spec like Notifications might choose to describe language and direction for a given notification message, on the theory that the message is meant to be consistent. This is probably okay if we're only talking about a couple of fields. The more fields that are included "under the metadata blanket", the more and more likely it is that one or another need a separate base direction (or less commonly, a separate language tag). (Note that when fields have their own metadata, assigning @dir and @lang in e.g. HTML becomes straightforward).

The problem *I* have is that there are many many specifications that need a convenient way to specify a natural language text field that includes the necessary metadata and provides for consistent serialization/deserialization/interchange. This is why this issue exists. 

(In case you're unaware of it, we have a document about this whole topic: [String-Meta](https://w3c.github.io/string-meta))

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/1025#issuecomment-932282447