- From: Felix Sasaki <fsasaki@w3.org>
- Date: Thu, 18 Jan 2007 11:15:50 +0900
- To: Sebastian Rahtz <sebastian.rahtz@oucs.ox.ac.uk>
- Cc: Yves Savourel <ysavourel@translate.com>, public-i18n-its@w3.org
Sebastian Rahtz wrote: > Felix Sasaki wrote: >> >>> New action item: Felix to see if the comparison tool can be smarter >>> about namespace compare. >>> >> >> could you bring me up to speed about what the issue is? >> > its the difference between this: > > <o:node path="/myMetaDoc/body[1]/insert[1]/z:书籍[1]/z:躯[1]/its:rules[1]"> > <o:output o:translate="yes"/> > > and this: > > <o:node path="/myMetaDoc/body[1]/insert[1]/z:书籍[1]/z:躯[1]/i:rules[1]" > outputType="default-value"> > <o:output o:translate="yes" /> > </o:node> > > because the namespace prefixes are in an attribute value, they are not > resolved, > and so come out as different. > > we may note that neother test1 nor expected declares the its: or i: > namespace, > so what this all means is open to doubt! I see the problem, but I'm not sure if we need to resolve it for the comparison tool. The path attribute is used within the tool to make sure that the same nodes are compared. We could use s.t. like this instead: <o:node path="/myMetaDoc/body[1]/insert[1]/z:书籍[1]/z:躯[1]/i:rules[1]" node-id="n-number" outputType="default-value"> <o:output o:translate="yes" /> </o:node> "number" in n-number counts the number of the node taking attributes and elements into account. I would still keep the path attribute because it makes it easier for humans to find the errors. Would that work for you? If yes, we have to change our implementations to produce s.t. like in http://www.w3.org/International/its/tests/test3/Translate1-result.xml and I would change the compare tool accordingly. Regards, Felix.
Received on Thursday, 18 January 2007 02:16:06 UTC