OASIS XML Localisation Interchange File Format (XLIFF) TC

----- "Rodolfo M. Raya" 

> 

                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                        
                                                        Original Message
                                                
                                                Original Message-----
> From: Asgeir Frimannsson [mailto:asgeirf@redhat.com]
> Sent: Tuesday, August 24, 2010 12:37 PM
> To: xliff
> Subject: Re: [xliff] Simplified XLIFF element tree
> 
> 
> I am trying to understand how your approach would work, but find it very
> hard to come up with a way of working with 'optional' unsegmented content.
> I think we do agree that a 

> It's very easy to segment text at the time of extraction.
> By doing this, you don't need unsegmented content in the 
> XLIFF file. I've been doing for many years and I can tell 
> you it works.

I have the feeling you are missing the point Rodolfo. We all know segmentation can be done when extracting.

The idea is that extraction and segmentation are two different actions, belong to two different domains, and that XLIFF must not assume all tools will work like one specific tool.



> I do not agree that the 

Hi everyone,

> For systems that have chosen to pre-segment,
> there should not be any compulsion to do 
> otherwise.

I completely agree.
And I didn't see any of the proposals so far trying to preventing a tool to pre-segment.


> I always viewed the the original 

Hi Asgeir, all,

A last note before closing the laptop for a full week off:


> after translation:
> 

I find that approach would be simple and easy to work with.

One possible slight change could be to always have at least one