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

Re: RV: [M2 milestone] Domain and Localization Note HTML output

From: Leroy Finn <finnle@tcd.ie>
Date: Thu, 20 Dec 2012 14:15:36 +0000
Message-ID: <CAMYWBwsJ7J14K8y6q1N4pJ9Mr5UtG4YGQZMFWLuVcT0=6=X3oQ@mail.gmail.com>
To: Pablo Nieto Caride <pablo.nieto@linguaserve.com>
Cc: Multilingual Web LT-TESTS Public <public-multilingualweb-lt-tests@w3.org>
I am uploading your output now. Also on the array brackets in HTML. It
would be easier if you could output it. But obviously if it is a massive
hassle then I suppose it would be fine to submit as you have it.
I don't know what the other think though??

Cheers,
Leroy


On 20 December 2012 12:13, Leroy Finn <finnle@tcd.ie> wrote:

> Sorry for the mix up I will upload this today.
>
> Thanks,
> Leroy
>
>
> On 20 December 2012 11:39, Pablo Nieto Caride <pablo.nieto@linguaserve.com
> > wrote:
>
>> Hi Leroy, Dom,****
>>
>> ** **
>>
>> I’ve just noticed that my output isn’t uploaded to the *
>> outputimplementors* in the github although Mauricio’s is. We sent it
>> separated so maybe that led you to confusion, sorry for that! I forward it
>> again in case you have misplaced the previous mail.****
>>
>> ** **
>>
>> On the other hand I asked you a question regarding the use of the index
>> on the elements’ path of the test suite output (at the end of mail below),
>> so if we’re going to use the index in all the elements, why not the html
>> too?****
>>
>> ** **
>>
>> Cheers,****
>>
>> Pablo.****
>>
>> ** **
>>
>> Hi Leroy, Dom,****
>>
>> ** **
>>
>> Find attached the output generated by our engine.****
>>
>> ** **
>>
>> Just a few considerations:****
>>
>> With respect to the definition of some of the features for HTML I think
>> they are not right.****
>>
>> **-          **Global - Linked rules      translate1html.html -> It’s ok*
>> ***
>>
>> **-          **Global - Linked rules <its:param>
>> translate6html.html -> It’s ok****
>>
>> **-          **Local - In host element translate2html.html -> It’s ok****
>>
>> **-          **Global (with //*) and local rules
>> translate3html.html -> It doesn’t have local rules but a local metadata**
>> **
>>
>> **-          **Global (with /doc) and local rules
>> translate4html.html -> It doesn’t have either local rules or a doc element
>> and has inheritance****
>>
>> **-          **Global and local rules (inheritance)
>> translate5html.html -> It doesn’t have inheritance****
>>
>> ** **
>>
>> As for Domain:****
>>
>> **-          **On the file domain2html.html the meta description is
>> <meta name="description" content="auto"/> and on the rules file the
>> domainMapping  is domainMapping="automotive auto, medical medicine,
>> 'criminal law' law, 'property law' law", in this case I think that the meta
>> description should be <meta name="description" content="automotive"/> so as
>> the output to be domains="auto".****
>>
>> * *
>>
>> **-          **On the file domain3html.html the meta description is
>> <meta name="description" content="sports"/> and on the rules file the
>> domainMapping  is domainMapping="'sports law' law, 'labor law' law,
>> 'contract law' law, 'competition law' law,'tort law' law", in this case I
>> think that the meta description should be <meta name="description"
>> content=" sports  law"/> so as the output to be domains="law" but the
>> output of the Test Suite says domains="sports", that doesn’t make much
>> sense, does it? ****
>>
>> ** **
>>
>> Finally regarding the output:****
>>
>> ** **
>>
>> I have a problem when printing the path of the elements, for instance for
>> the test file translate2html.html the Test Suite output is:****
>>
>> /html    translate="yes"****
>>
>> /html/head[1]  translate="yes"****
>>
>> /html/head[1]/meta[1]               translate="yes"****
>>
>> /html/head[1]/meta[1]/@charset         translate="no"****
>>
>> /html/head[1]/title[1]  translate="yes"****
>>
>> /html/body[1]  translate="yes"****
>>
>> /html/body[1]/p[1]       translate="yes"****
>>
>> /html/body[1]/p[1]/span[1]      translate="no"****
>>
>> /html/body[1]/p[1]/span[1]/@translate             translate="no"****
>>
>> /html/body[1]/p[1]/span[2]      translate="no"****
>>
>> /html/body[1]/p[1]/span[2]/@translate             translate="no"****
>>
>> ** **
>>
>> Mine is:****
>>
>> /html    translate="yes"****
>>
>> /html/head        translate="yes"****
>>
>> /html/head/meta           translate="yes"****
>>
>> /html/head/meta/@charset     translate="no"****
>>
>> /html/head/title             translate="yes"****
>>
>> /html/body        translate="yes"****
>>
>> /html/body/p   translate="yes"****
>>
>> /html/body/p/span[1] translate="no"****
>>
>> /html/body/p/span[1]/@translate        translate="no"****
>>
>> /html/body/p/span[2] translate="no"****
>>
>> /html/body/p/span[2]/@translate        translate="no"****
>>
>> ** **
>>
>> The problem is that when the element doesn’t have a sibling PHP doesn’t
>> print the array brackets, e.g. head, meta, title, body, p… in this example,
>> since there is only just one element I don’t consider it wrong but I
>> imagine that you will have problems comparing this file with the Test
>> Suite’s. I can try to find a workaround if you this troublesome.****
>>
>> ** **
>>
>> Thank you!****
>>
>> *__________________________________*
>>
>> *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: **pablo.nieto@linguaserve.com***
>>
>> *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.”*
>>
>> *__________________________________*****
>>
>
>
Received on Thursday, 20 December 2012 14:16:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 December 2012 14:16:08 GMT