Re: XLIFF maping layout

+1

Also, I suggest we progress the XLIFF1.2 and 2.0 mapping on different 
pages so we can focus on completing and publishing the 1.2 mapping as a 
best practice document without waiting for the 2.0 spec to complete.

Also, I think it would be a good idea to develop a more comprehensive 
set of examples alongside the testsuite on github. This will be a good 
tool to encourage uptake and we can then extract more correct sample 
fragments to ehnance the mapping pages.

I think we'd need two sets of examples
1) showing best practice when mapping from our existing test suite input 
into XLIFF as per:
https://github.com/finnle/ITS-2.0-Testsuite/tree/master/its2.0/xliffsamples
But perhaps extended with more realistic examples with mappings from 
source files with multiple data categories

2) showing best practice when adding ITS annotation directly into an 
exisitng XLIFF file, along the lines of the (now a bit out of date) 
XLIFF rountrip example at:
https://github.com/finnle/ITS-2.0-Testsuite/tree/master/its2.0/xliffsamples/roundtrip-example

cheers,
Dave

On 17/05/2013 14:49, Yves Savourel wrote:
> Hi all,
>
> Could we start moving the mapping from the table to a more easy reading layout?
> The table is getting less and less readable, and is a lot more difficult to edit than normal paragraphs. It would also allow concurrent edit on the page as long as it's on different sections.
>
> I've done Translate as an example, here:
> http://www.w3.org/International/its/wiki/XLIFF_Mapping#Data_Categories
>
> We could progressively move each data category from the table to the section as we have time.
>   
> -ys
>
>
>

Received on Saturday, 18 May 2013 13:17:35 UTC