OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi all,

My initial thoughts on the subject of segmentation:

1) There are going to be times when the "extraction unit" (e.g. a docbook 

Hi,

Of course many times a 

>...You can segment the 

Hi again,

There are two different issues to consider:

1) How to represent a single segment. 
2) How to represent segmentation information in an XLIFF file. 

I propose to use 

> As Andrzej suggested, a "text block" can be represented using 
> the existing 

Hi,

If you want to separate "extracted text" from "segmented text", you can use a new element to contain unsegmented extracted text and the traditional 

The Ektron CMS currently does not support XLIFF 1.2's seg-source. It extracts and merged and does not perform linguistic segmentation (leaving that for the translation tools). However, if the XLIFF file comes back segmented, it may not be able to perform the merge.

Doug



                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                        
                                                        Original Message
                                                
                                                Original Message-----
From: Asgeir Frimannsson [mailto:asgeirf@redhat.com] 
Sent: Monday, August 23, 2010 7:21 AM
To: xliff
Subject: Re: [xliff] Simplified XLIFF element tree

Hi all,

My initial thoughts on the subject of segmentation:

1) There are going to be times when the "extraction unit" (e.g. a docbook 

Hi Doug,

> However, if the XLIFF file comes back segmented, 
> it may not be able to perform the merge.

That sounds strange to me. In all cases the translated file should have the same 

Yves,

To my knowledge, no one has tried importing XLIFF with the added