[i18n-activity] I18N string best practices vs. design-principles (#1765)

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

== I18N string best practices vs. design-principles ==
**This is a tracker issue.** Only discuss things here if they are i18n group internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**

ยง https://github.com/w3ctag/design-principles/issues/454


Instructions _(delete this line and all following)_:
- check for the following labels, then remove the PENDING label, then delete these instructions

- Check that TRACKER & S:... labels are there
- **Add t:... label(s) to indicate the topic (same as ids in specdev)**


- If urgent add:
- add ADVICE-REQUESTED label if the WG-issue is specifically asking for i18n to advise/comment
- add NEEDS-ATTENTION label if this is an important issue

- if there's an i18n-*lreq label in the WG repo check for:
   -  ...LREQ label(s) there should be one or more
   - SPEC-TYPE-ISSUE label (dark green background) should be there
   - TYPE-INFO-REQUEST label (red background) if this is a WG-issue that constitutes a request for script/language expert advice
   - i:... label(s) to indicate the Language Enablement Index category

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


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

Received on Friday, 6 October 2023 10:15:08 UTC