- From: Takeshi Kanai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Aug 2016 09:36:29 +0000
- To: public-annotation@w3.org
@gsergiu +1 for clarification. I think it is also important to consider who should decide the value of the dc:language in the annotation's life cycle. If dc:language can not fulfill important use cases, we will need to use processingLanguage instead. Then we can set a line between the two attributes, right? Due to Unicode CJK unified ideographs issue, a language attribute is necessary to render text correctly, and I would like to clarify which language value should be applied for that purpose. I think the image in the link below would help understanding what is the issue and why it is necessary to set a language attribute for rendering text. https://gist.github.com/tkanai/c9d64283ae14ecc5250f -- GitHub Notification of comment by tkanai Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/337#issuecomment-237807104 using your GitHub account
Received on Friday, 5 August 2016 09:36:37 UTC