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

RE: [spec] question

From: Pedro L. Díez Orzas <pedro.diez@linguaserve.com>
Date: Fri, 20 Jul 2012 11:15:38 +0200
To: "'Arle Lommel'" <arle.lommel@dfki.de>, "'Multilingual Web LT Public List'" <public-multilingualweb-lt@w3.org>
Message-ID: <06d301cd6658$3a483ba0$aed8b2e0$@linguaserve.com>
Dear Arle, 

 

Perhaps refers to the use of extension rules
(http://itstool.org/extensions/). For example, we are going to implement
“readiness”, in spite is not in the ITS 2.0 short list, since in Real Time
Translation Systems we do not have any other means to express in the HTML5
generated by the client that a certain web page have to be post edited, the
priority and if the RTTS have to show the machine translated page without
post edition or it has to wait until it is post edited. To do this, since it
is not included, we will have a look to this extensions.

 

Also see http://www.w3.org/TR/2012/WD-its2req-20120524/#Process_Model. 

 

I don’t know if this is related to your question.

 

Best,

Pedro

 

 

De: Arle Lommel [mailto:arle.lommel@dfki.de] 
Enviado el: viernes, 20 de julio de 2012 10:59
Para: Multilingual Web LT Public List
Asunto: [spec] question

 

Hello all,

 

I've got a quick question about a passage in the spec that I find very
confusing:

 

This standard does not cover all mechanisms and data formats (sometimes
called Localization Properties) that might be needed for configuring
localization workflows or tools to process a specific format. However, these
mechanisms and data formats may be implemented using the framework described
in this standard.

 

If I follow this, it is simply saying that there will be some things needed
to support localization that simply remain outside the scope of this
document (e.g., most of the requirements bits that won't make it in the
spec), which seems right. But then what does the second sentence mean? It
seems to be saying that there is a bunch of stuff outside the scope of this
document but you can implement it using what is in this document. But that
doesn't make sense. Let's suppose I want to implement a mechanism to use
translation parameters (a data format from Linport) along with the
translation. There is nothing in the "framework described in this standard"
to tell me how to do that, and this statement therefore seems misleading.

 

Maybe I'm missing an obvious interpretation, but I just don't get what this
means. So I do think it needs to be clearer. Can anyone help clarify the
intent here?

 

-Arle
Received on Friday, 20 July 2012 09:16:39 UTC

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