- From: Pablo Nieto Caride <pablo.nieto@linguaserve.com>
- Date: Mon, 12 Nov 2012 13:37:42 +0100
- To: "'Yves Savourel'" <ysavourel@enlaso.com>, "'Multilingual Web LT-TESTS Public'" <public-multilingualweb-lt-tests@w3.org>
- Message-ID: <08ac01cdc0d2$82073cf0$8615b6d0$@linguaserve.com>
I think that is clearer that way, my +1 to this.
Cheers,
__________________________________
Pablo Nieto Caride
Dpto. Técnico/I+D+i
Linguaserve Internacionalización de Servicios, S.A.
Tel.: +34 91 761 64 60 ext. 0422
Fax: +34 91 542 89 28
E-mail: <mailto:pablo.nieto@linguaserve.com> pablo.nieto@linguaserve.com
www.linguaserve.com <http://www.linguaserve.com/>
«En cumplimiento con lo previsto con los artículos 21 y 22 de la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de Información y Comercio Electrónico, le informamos que procederemos al archivo y tratamiento de sus datos exclusivamente con fines de promoción de los productos y servicios ofrecidos por LINGUASERVE INTERNACIONALIZACIÓN DE SERVICIOS, S.A. En caso de que Vdes. no deseen que procedamos al archivo y tratamiento de los datos proporcionados, o no deseen recibir comunicaciones comerciales sobre los productos y servicios ofrecidos, comuníquenoslo a clients@linguaserve.com, y su petición será inmediatamente cumplida.»
"According to the provisions set forth in articles 21 and 22 of Law 34/2002 of July 11 regarding Information Society and eCommerce Services, we will store and use your personal data with the sole purpose of marketing the products and services offered by LINGUASERVE INTERNACIONALIZACIÓN DE SERVICIOS, S.A. If you do not wish your personal data to be stored and handled, or you do not wish to receive further information regarding products and services offered by our company, please e-mail us to clients@linguaserve.com. Your request will be processed immediately.”
__________________________________
De: Yves Savourel [mailto:ysavourel@enlaso.com]
Enviado el: lunes, 12 de noviembre de 2012 13:17
Para: 'Multilingual Web LT-TESTS Public'
Asunto: RE: Test Suit Specs - Standoff Markup
+1
From: Leroy Finn [mailto:finnle@tcd.ie]
Sent: Monday, November 12, 2012 3:02 AM
To: Felix Sasaki
Cc: Fredrik Liden; Multilingual Web LT-TESTS Public
Subject: Re: Test Suit Specs - Standoff Markup
I haven't started on localisation quality parsing yet but i would go with the pattern of alphabetical ordering. What do others think?
Leroy
On 12 November 2012 10:01, Leroy Finn <finnle@tcd.ie> wrote:
I haven't start on localisation quality parsing yet but i would go with the pattern of alphabetical ordering. What do others think?
Leroy
On 10 November 2012 05:03, Felix Sasaki <fsasaki@w3.org> wrote:
+1. Would it make sense to say in the test suite description that the elements inside standoff markup are ordered alphabetically?
- Felix
2012/11/9 Fredrik Liden <fliden@enlaso.com>
I think testoutput for standoff markup is undefined, especially for multiple entries applied to the same target.
In case Leroy needs some feedback maybe you can think about how to best represent the test output of this test file, Example 84:
<?xml version="1.0"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2"
xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
<file original="example.doc" source-language="en" datatype="plaintext">
<body>
<trans-unit id="1">
<source xml:lang="en">This is the content</source>
<target xml:lang="fr"><mrk mtype="x-itslq"
its:locQualityIssuesRef="#lq1">c'es</mrk> le contenu</target>
<its:locQualityIssues xml:id="lq1">
<its:locQualityIssue locQualityIssueType="misspelling"
locQualityIssueComment="'c'es' is unknown. Could be 'c'est'"
locQualityIssueSeverity="50"/>
<its:locQualityIssue locQualityIssueType="typographical"
locQualityIssueComment="Sentence without capitalization"
locQualityIssueSeverity="30"/>
</its:locQualityIssues>
</trans-unit>
</body>
</file>
</xliff>
In the common cases we to just display the IRI of the hrefs such as locNoteHrefPointer. But in the case of standoff we probably want o resolve the values to validate the result. Here’s basic example, putting the numbers in front so we can still sort it. It’s not that pretty though.
/xliff/file[1]/body[1]/trans-unit[1]/target[1]/mrk locQualityIssuesRef="#lq1"(?) [1]locQualityIssueType="misspelling" [1]locQualityIssueComment="'c'es' is unknown. Could be 'c'est'" [1]locQualityIssueSeverity="50" [2]locQualityIssueType="typographical" [2]locQualityIssueComment="Sentence without capitalization" [2]locQualityIssueSeverity="30"
Fredrik
--
Felix Sasaki
DFKI / W3C Fellow
Received on Monday, 12 November 2012 12:38:11 UTC