[PARENT TRACKING ISSUE] for String-Meta

[aphillips]

This issue is being used to coordinate communications and status for all of the specs and working groups that I18N has filed issues against related to language or direction metadata and who are blocked by our request to TC39.

Links

• The String-Meta document and its editor's copy
• The document Use cases for bidi and language metadata on the Web is a useful read
• We had a W3C TAG request here
• We have an explainer here

Related Issues

Active Issues

• PaymentCredentialInstrument dictionary does not include language/direction metadata #1411 (Secure Payment Confirmation)
• Add dir/lang member on dictionaries whose content is displayed in browser UI payment-request#327 (Payment Request)
• 'label' needs direction and language metadata mediacapture-main#665 (Media Capture and Streams)
• Human readable error message without language info mediacapture-screen-share#135 (Screen Capture)
• Language and direction metadata for human-readable messages #1503 (WebGPU)

Inactive Issues

These are issues that are either closed or are not being actively worked on as the spec has progressed to CR or later.

• A number of vocabulary items need language/direction/etc. metadata #193 (Vocab-duv)
• Add text language / direction attributes #248 (Web Share)
• no way to indicate direction or language of name Micropub#37 (Micropub)
• Message text not localizable webrtc-pc#1605 (WebRTC)

[plehegar]

The behavior of w3cbot is infllux, see w3c/horizontal-issue-tracker#35

[r12a]

@plehegar fwiw, note that @aphillips originally set up this issue with § before each link in the Related Issues list and with a needs-resolution label, but we determined during our meeting that that is inappropriate, because this is not the normal kind of issue. We therefore removed all the § symbols and the label.

[aphillips]

[Updated per action-1205]. Note that I corrected the link to WebRTC in this edit.