OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only

  • 1.  RE: [xliff] Cloning of

    Posted 01-26-2005 10:50 
     MHonArc v2.5.0b2 -->

















    xliff message
    







    [Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]
    


    







    Subject: RE: [xliff] Cloning of <g> elements
    







    



    Title: Message
    

    



    Hi 
Magnus,
    

     
    

    I believe that 
(a) is a reasonable assumption to make. If you don't carry across all the 
attributes (DNA?) of the original tag then would it really be a 
clone?
    

     
    

    As I understand 
it, the cloning ability is there primarily to allow for formatting that needs to 
be split in the <target> element because the original 
text span has been split in the translation. For example:
    

     
    

    <source>The <g id="1" ctype="bold">big black</g> 
cat.</source>
    

    <target>The <g id="1" ctype="bold">gros</g> chat <g 
id="1" ctype="bold">noir</g>.</target>
    

     
    

    I understand that 
you might want to clone the <source> tags in order to 
segment the original source text. Although I'm not overly familiar with the work 
of the segmentation subcommittee I would guess that you're looking to introduce 
something along the lines of <seg>....</seg> in the 
<source> element and that XML rules dictate that you're 
not allowed to have <seg>...<g>...</seg> so 
you'd be looking to replace this with 
<seg>...<g>...</g></seg><g> with 
the <g> being cloned (I have an HTML verifier which does 
something similar).
    

     
    

    What makes me 
nervous is the fact that the <g> might not be "clonable" 
and that the original XLIFF filter wouldn't be able to handle multiple 
occurrences of a particular <g> tag. Is there a reason 
why it's not possible to simply use an empty <seg/> tag 
to indicate where the text should be segmented? This would mean that you 
wouldn't have to clone elements from the original 
<source> and also has the added advantage that 
this element can simply be ignored when the XLIFF file is merged later in the 
process.
    

     
    

    FWIW, I 
think that an element would have to have an explicit 
clone="yes" before it can be cloned with 
confidence.
    

     
    

    Regards
    

     
    

    David Pooley
    Software 
Architect
    SDL International
    

     
    

     
    

    


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                
    
                                                
                                            
    
                                        

                                        
                                        

                                    
			

                                    
                                

                                
                                
    
                                
    
                            
		
                
        
    




            
        
    


	
    


    
    
         
    
    Related Content