[i18n-activity] APA Personalization TF I18N Self Review: Adaptable Content Module (#862)

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

== APA Personalization TF I18N Self Review: Adaptable Content Module ==
Here is a link to our explainer document which may help for context.
[Personalization Semantics Explainer 1.0](https://www.w3.org/TR/personalization-semantics-1.0/)

[Personalization Semantics Content Module 1.0](https://www.w3.org/TR/personalization-semantics-content-1.0/)

 If the spec (or its implementation) contains any natural language text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc),
Answer: N/A.

  If the spec (or its implementation) allows content authors to produce typographically appealing text, either in its own right, or in association with graphics.

Answer: We are using numerical tokens which can be mapped to symbols sets, so we don't think this is an issue but request you look at this closer. Also the symbol sets themselves may be localized.
[Spec symbol](https://www.w3.org/TR/personalization-semantics-content-1.0/#symbol-explanation)

  If the spec (or its implementation) allows the user to point into text, creates text fragments, concatenates text, allows the user to select or step through text (using a cursor or other methods), etc.

Answer: Simplification allows for replacing sections of text with an alternative text, which the author will provide.
[Simplification](https://www.w3.org/TR/personalization-semantics-content-1.0/#simplification-explanation)

  If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers
Answer: N/A

  If the spec (or its implementation) sorts text
Answer: N/A

  If the spec (or its implementation) captures user input
Answer: N/A

  If the spec (or its implementation) deals with time in any way that will be read by humans and/or crosses time zone boundaries
Answer: N/A

  If the spec (or its implementation) allows any character encoding other than UTF-8.

Answer: We support UTF-8 but we anticipates supporting UTF-16 for symbol sets and there is nothing in our spec that would prevent this.

  If the spec (or its implementation) defines markup.

Answer:We do define attribute names and values as tokens that are human readable but we don't expect those to be localized. However we do have content simplification that does have alternative text descriptions.
[Simplification](https://www.w3.org/TR/personalization-semantics-content-1.0/#simplification-explanation)

  If the spec (or its implementation) deals with names, addresses, time & date formats, etc
Answer:data-purpose attribute does pattern after autocomplete attribute of HTML5 and author is responsible for any internationalization concerns.

  If the spec (or its implementation) describes a format or data that is likely to need localization.

Answer: data-purpose attribute does pattern after autocomplete attribute of HTML5 and author is responsible for any internationalization concerns.

  If the spec (or its implementation) makes any reference to or relies on any cultural norms

Answer: there are internationalized AAC symbol sets to address that concern. and we are supporting those translations

---
**WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered.

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

Received on Monday, 2 March 2020 16:24:13 UTC