W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > August 2012

mlw-lt-track-ISSUE-45 (its-api-for-html5): Do we need an ITS API for HTML5?

From: MultilingualWeb-LT Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 21 Aug 2012 14:39:51 +0000
Message-Id: <E1T3pcV-00034W-6D@tibor.w3.org>
To: public-multilingualweb-lt@w3.org
mlw-lt-track-ISSUE-45 (its-api-for-html5): Do we need an ITS API for HTML5?


Raised by: Felix Sasaki
On product: 

We had discussed this before, and I assume that most of the people would say: no. ITS processing is done outside of the browser, or very different things happen to the same data category (e.g. "translate": do MT, do pseudo translate, transform to XLIFF; ...) so why having an API for HTML5?

One answer might be: making it easier to create applications in the browser based on ITS. For these, having just one method that takes an element / attribute node as an input and gives back ITS information would be helpful.

Also I would like to create some working group consensus on this before or meeting with the HTML working group in Lyon.
Received on Tuesday, 21 August 2012 14:39:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:51 UTC