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

RE: [bug/issue] Localization Quality Issue

From: Yves Savourel <ysavourel@enlaso.com>
Date: Wed, 12 Dec 2012 09:25:01 -0700
To: "'Multilingual Web LT-TESTS Public'" <public-multilingualweb-lt-tests@w3.org>
Message-ID: <assp.0693bc5129.assp.0693ccfc38.002701cdd885$3c68e610$b53ab230$@com>
I've committed the few output files (for HTML) that were not matching the input data.
(e.g. "Sentence..." in the input data vs "sentence..." in the output, etc.)

Will work on XML later.

cheers,
-yves


-----Original Message-----
From: Yves Savourel [mailto:ysavourel@enlaso.com] 
Sent: Wednesday, December 12, 2012 8:03 AM
To: 'Multilingual Web LT-TESTS Public'
Subject: [bug/issue] Localization Quality Issue

Hi Leroy, all,

I've started to look at the LQI files are here are a few notes for the HTML files (I'll work on XML later).


-- Several files have at the same time a locQualityIssuesRef and other attributes: we can't have that. The data is either in the standoff markup or directly set the selected element (globally or locally).

-- locqualityissue7html.html output lists the XML code that is in <script>. That's incorrect: from the HTML tree viewpoint the content of <script> is not a sub-tree.

-- It locQualityIssueEnabled is output only when it's defined. But this data has a default (yes), so I would suggest to output it either: each time there is LQI data on the node, or only when it is not the default. Why? Some implementation may not be able to know whether or not the value is coming from default or if it was explicitely declared.

-- The output for locqualityissue8html.html has some info set to the p element rather than the p/span.

-- A couple of output files seemed to be output of old input. I've committed the new output.

cheers,
-yves
Received on Wednesday, 12 December 2012 16:25:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 December 2012 16:25:33 GMT