[i18n-activity] Language and direction metadata for human-readable messages (#1503)

xfq has just created a new issue for https://github.com/w3c/i18n-activity:

== Language and direction metadata for human-readable messages ==
## Proposed comment

From the [short i18n review](https://github.com/gpuweb/gpuweb/issues/2546) of WebGPU and WGSL:

> The WebGPU API contains several `DOMString` that are reasonably expected to be surfaced to a human:
> - [GPUCompilationMessage.message](https://gpuweb.github.io/gpuweb/#dom-gpucompilationmessage-message) which is a compiler message from the WGSL compiler.
> - [GPUDeviceLostInfo.message](https://gpuweb.github.io/gpuweb/#dom-gpudevicelostinfo-message) that may describe in human-readable language the reason why the GPU was lost (it was disconnect, timed out, etc).
> - [GPUValidationError.message](https://gpuweb.github.io/gpuweb/#dom-gpuvalidationerror-message) which describe in human-readable language what error happened (similarly to `DOMException.message`, see the [explainer](https://gpuweb.github.io/gpuweb/explainer/#errors) for why it is different)
> - [GPUCompilationMessage](https://gpuweb.github.io/gpuweb/#gpucompilationmessage) points at a location in a user-provided string by line number, position on the line, string offset, and length.
> - The WebGPU adapter identifier, depending on the resolution surrounding the [GPU Adapter Identifier](https://github.com/gpuweb/gpuweb/blob/main/design/AdapterIdentifiers.md) discussions. The information surfaced to the user may contain the GPU's vendor name, chip name, or other information.
> The expectation is to use ["first-strong"](https://w3c.github.io/string-meta/#firststrong) augmented with Unicode markers if need be. The implementations will have to decide when to add the markers.

First-strong is only recommended as a fallback for the base direction metadata, and there is currently no way for identifying the language of these messages. Natural language error message fields, when provided, should include language and direction metadata. See https://w3c.github.io/bp-i18n-specdev/#errors for more info.

## Instructions: 

This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. Create the review comment you want to propose by replacing the prompts above these instructions, but **LEAVE ALL THE INSTRUCTIONS INTACT** 

2. Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.

3. Ask the i18n WG to review your comment.

4. After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-\*lreq label(s).

5. Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use \[...](...) notation – you need to delete the placeholder, then paste the URL.

6. Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue. 

7. If you added an \*lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.

8. Edit this issue to **REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT**, ie. the line below that is '---' and all the text before it to the very start of the issue.


**This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**

§ url_for_the_issue_raised

Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1503 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 2 April 2022 06:06:37 UTC