OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi Rodolfo, all,

>> It seems it would be simpler to have one element for each extracted 
>> unit, and the un/segmented information inside that element: Any type
>> of parser can access all of it at once, no need for linking or other
>> extra mechanism; finding/fixing/editing files is easier; etc.
> 
>
> Please keep unsegmented information separate from translatable segments. 
> Like Andrzej, I don't plan to put unsegmented text in my XLIFF files.
> A common parent for unsegmented/segmented would be annoying unless it 
> is optional.
>
> Unsegmented text should be optional, as it is not needed for translating
> a segmented XLIFF. Unsegmented text should not be in the core XLIFF 
> module, it should live in a separate optional namespace.


Having the un-segmented text not part of the core and living in a separate optional namespace is a strange idea.

The first goal of XLIFF is to represent extracted text, not segmented extracted text.
The representation of the segmentation is what should be optional.

Cheers,
-ys

> 

                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                        
                                                        Original Message
                                                
                                                Original Message-----
> From: Yves Savourel [mailto:ysavourel@translate.com]
> Sent: Tuesday, August 24, 2010 9:23 AM
> To: 'xliff'
> Subject: RE: [xliff] Simplified XLIFF element tree
> 
> Hi Rodolfo, all,
> 
> >> It seems it would be simpler to have one element for each extracted
> >> unit, and the un/segmented information inside that element: Any type
> >> of parser can access all of it at once, no need for linking or other
> >> extra mechanism; finding/fixing/editing files is easier; etc.
> >
> >
> > Please keep unsegmented information separate from translatable
> segments.
> > Like Andrzej, I don't plan to put unsegmented text in my XLIFF files.
> > A common parent for unsegmented/segmented would be annoying unless
> it
> > is optional.
> >
> > Unsegmented text should be optional, as it is not needed for translating
> > a segmented XLIFF. Unsegmented text should not be in the core XLIFF
> > module, it should live in a separate optional namespace.
> 
> 
> Having the un-segmented text not part of the core and living in a separate
> optional namespace is a strange idea.
> 
> The first goal of XLIFF is to represent extracted text, not segmented
> extracted text.
> The representation of the segmentation is what should be optional.

Text should be segmented in order to be translated. Unsegmented text is not required for translating.

In the last sample tree I sent I included elements for holding unsegmented text (

My assumption was that using 

Hi David,

I don't like and don’t use 

Hi all,
It seems that most of us are more or less comfortable with having an extra layer for unsegmented, just extracted.. Same as Yves I believe that the unsegmented should be obligatory. But people like Andrzej and Rodolfo may have valid reasons for doing it the other way round..[although I agree with Asgeir and Yves that Andrzej can have more robust relationship with xml:tm in the new proposed setting]

I believe that we do not get any further without some solid use case analysis
IMHO we need to figure out rather combinatorically  what is the hierarchical relationship of

Hi David,

I will not attend to the face to face meeting in Limerick so I prefer this issue to be discussed via email or in the next regular meetings.

Let me summarize my position:

- I don't care if some tools include unsegmented text in their XLIFF files if my tools can safely ignore it.
- I don't want to include unsegmented text in the XLIFF files generated by my tools.
- If unsegmented text is present in a file, I want it to be clearly separated from translatable segments.

Regards,
Rodolfo
--
Rodolfo M. Raya