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

Re: ACTION-447: Make a batch transformation of the test suite to xliff

From: Dave Lewis <dave.lewis@cs.tcd.ie>
Date: Thu, 21 Feb 2013 11:08:08 +0000
Message-ID: <51260018.7000006@cs.tcd.ie>
To: Yves Savourel <ysavourel@enlaso.com>
CC: 'Mārcis Pinnis' <marcis.pinnis@Tilde.lv>, 'Multilingual Web LT Public List Public List' <public-multilingualweb-lt@w3.org>
Hi Yves, Marcis,
There's some indication in you discussion that localeFilter and 
translate work in a similar way in the source to XLIFF mapping. My 
assumptionis that locale filter is specifically there to prevent 
extraction of annotate text when generating XLIFF for a specific target 
language - similar to what you describe.

I'm not convinced that translate works in the same way since we may want 
to include the content in the XLIFF as 'protected' source content to 
provide context for the human translators (it can also provide content 
to text analytics components called from the XLIFF process)

We therefore need to nail down in best practice how exactly 
translate='no' content should be processed in the mapping and extracting 
one, e.g. if the _whole_ document is annotated in this way should it be 
extracted at all, since its not really acting as 'context' in this way.


On 19/02/2013 13:10, Yves Savourel wrote:
>> 2. With the Locale Filter I see that instead of having ITS 2.0 mark-up,
>> >the whole fragment has been removed and replaced with a placeholder
>> >(is that because it is not possible to add Locale Filter mark-up in
>> >XLIFF at all?). This does not preserve the content, but filters out
>> >fragments based on ITS 2.0 consumption/production Use Case scenarios
>> >(which is I guess an internal process and not for data exchange purposes).
>> >And ... it actually does not show an XLIFF document with the Locale Filter
>> >data category metadata in it (that was what we wanted to see, but the
>> >examples, I believe do not show that). Is this because XLIFF would not be
>> >able to handle ITS 2.0 annotation or because of some other reasons
>> >(I am a bit confused here ... so I would like to clarify)?
> In this case the data category is implemented by the filter. You guessed correctly: The filter filters out the source parts not for the target locale (basically treat them like if they were with translate='no').
Received on Thursday, 21 February 2013 11:08:44 UTC

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