W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > February 2013

RE: Issue-55: RE: ACTION-447: Make a batch transformation of the test suite to xliff

From: Yves Savourel <ysavourel@enlaso.com>
Date: Thu, 21 Feb 2013 06:53:03 -0700
To: "'Multilingual Web LT Public List Public List'" <public-multilingualweb-lt@w3.org>
Message-ID: <004401ce103a$c5949640$50bdc2c0$@com>
For this one:

> - If we just put the result of termInfoPointer, termInfoRef and termInfoRefPointer 
> in comment and let the user deal with URI vs text: how can that be processed by an 
> ITS-only tool? You cannot have a global rule like this:
> <its:termRule selector="//mrk[@mtype='term']" term='yes'
> termInfoPointer="@comment" termInfoRefPointer="@comment"/> The comment attribute can be either but not both.

How about we use comment for text (i.e. from termInfoPointer)
and its:termInfoRef for URI (i.e. from termInfoRef or termInforefPointer)?

That way there is a clear distinction between the two types of information.

that still doesn't solve mapping the text info back into the original document, but it's a small progress.

Received on Thursday, 21 February 2013 13:53:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:04 UTC