[i18n-activity] Description of language tags broken (#1706)

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

== Description of language tags broken ==
## Proposed comment

`lang` member
https://w3c.github.io/manifest/#lang-member

> A language tag is a [string](https://infra.spec.whatwg.org/#string) that matches the production of a Language-Tag defined in the [[BCP47](https://w3c.github.io/manifest/#bib-bcp47)] specifications (see the [IANA Language Subtag Registry](https://www.iana.org/assignments/language-subtag-registry) for an authoritative list of possible values). That is, a language range is composed of one or more subtags that are delimited by a U+002D HYPHEN-MINUS ("-"). For example, the 'en-AU' language range represents English as spoken in Australia, and 'fr-CA' represents French as spoken in Canada. Language tags that meet the validity criteria of [[RFC5646](https://w3c.github.io/manifest/#bib-bcp47)] section 2.2.9 that can be verified without reference to the IANA Language Subtag Registry are considered structurally valid.

The above description has multiple issues. Rather than dissect them individually, I would suggest replacing the above with this paragraph:

> A language tag is **well-formed** language tag consisting of a [string](https://infra.spec.whatwg.org/#string) that matches the production `Language-Tag` defined in BCP47. Note that language tags are _case insensitive_. Examples of language tags include `fr` (French), `en-AU` (English as spoken in Australia), or `zh-Hans-CN` (Chinese as written in the Simplified Han script as spoken in China).

Additional specification guidance on this topic can be found here: https://www.w3.org/TR/international-specs/#lang_values


## 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. **Add one or more t:... labels. These should use ids from specdev establish a link to that doc.**

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/1706 using your GitHub account


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

Received on Monday, 8 May 2023 15:18:21 UTC