[activitystreams] Issue: How to know the language of a natural language value when there is no translation? marked as i18n

r12a has just labeled an issue for 
https://github.com/w3c/activitystreams as "i18n":

== How to know the language of a natural language value when there is 
no translation? ==
Please Indicate One: 
 * [ ] Editorial
 * [ ] Question
 * [ ] Feedback
 * [x] Blocking Issue
 * [ ] Non-Blocking Issue

[This issue has support from others in the i18n WG.]

For example at 
https://www.w3.org/TR/activitystreams-core/#naturalLanguageValues

It is often important for rendering to know the language of the 
natural language text, ie. for automatic selection of appropriate 
fonts when dealing with Chinese vs Japanese, for line breaking rules, 
for pronunciation by voice browsers, for automated translation, for 
hyphenation, etc...

Therefore there needs to be a way to identify the language of every 
item of natural language text.

The explanations in the spec currently seem to imply that `nameMap`, 
etc, are only used when there are multiple translated versions 
available, and that if you use `name` there is no way to indicate the 
language of the text. (If this is an incorrect interpretation, there 
should at least be a note to clarify it.)

We would like you to provide a simple way of identifying the language 
of `name`, `summary` and `content` properties.

If there is no straightforward way to do this, we think the spec 
should at least indicate the importance of providing language 
information and encourage people to use the `xxxMap` property by 
default rather than the alternative, so that language information can 
be carried, eg. 

```
{...
"contentMap": { "en": "A simple note" }
}
```
and change the examples to reflect that.




See https://github.com/w3c/activitystreams/issues/335

Received on Friday, 8 July 2016 14:01:56 UTC