[i18n-activity] 'script' property may not be properly specified, may be incorrect choice? (#1457)

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

== 'script' property may not be properly specified, may be incorrect choice? ==
Paint Text
[link_to_spec](https://w3c.github.io/imsc-hrm/spec/imsc-hrm.html#paint-text)

> Script property (see Standard Annex #24 at [UNICODE]) for the character of gi
>> latin, greek, cyrillic, hebrew or base

The name 'base' in the table assigning *Normalized glyph copy performance factor (GCpy)* does not correspond to script properties in Unicode. There are two possibilities here: `Common` and `Inherited`. It seems like `Common` is the value desired here. FWIW, the other script names should probably be rendered they way Unicode does, in title case (e.g. `Latin`, `Greek`, etc.) or perhaps using the ISO15924 codes (`Latn`, `Grek`, `Cyrl`, `Hebr`).

It is unclear why these specific scripts are assigned a "performance factor" 4x other characters. Many scripts have similar structure to these and might also want a higher performance factor?

---
Instructions: 

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

1. **CREATE A PROPOSED REVIEW COMMENT BY REPLACING THE PROMPTS ABOVE THIS PARAGRAPH, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** Then ask the i18n WG to review your comment.

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 staffer to help.

3. After discussion with the i18n WG, raise this issue to the WG that owns the spec. Use the text above this para as the basis for that comment.

4. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue. Do NOT remove the initial '§ '.

5. Edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT.

6. Remove the 'pending' label.



**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:**


§ link_to_issue_raised


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


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

Received on Monday, 31 January 2022 16:01:03 UTC