[i18n-activity] Short_but_informative_title_here (#1485)

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

== Short_but_informative_title_here ==
## Proposed comment

(See Example 5)

> A real-world example of [custom property](https://www.w3.org/TR/css-variables-1/#custom-property) usage is easily separating out strings from where they’re used, to aid in maintenance of internationalization:
:root:lang(en) {--external-link: "external link";}
:root:lang(de) {--external-link: "externer Link";}

a[href^="http"]::after {content: " (" var(--external-link) ")"}
> The variable declarations can even be kept in a separate file, to make maintaining the translations simpler.

This is perhaps questionable advice? On the one hand, if one has static strings in one's style sheet, using a variable and the `:lang` selector might be useful as a way of localizing the strings without repetition. On the other hand, there is some complexity to language matching here and it's probably not a best practice to have strings embedded in this way anyway.

Also note that the choice of German here isn't perhaps immediately illustrative. Choosing a language such as French whose translation is more visually distinct might help understanding.

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

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

Received on Tuesday, 1 March 2022 16:59:45 UTC