MHonArc v2.5.0b2 -->
















xliff message






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

--

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








Subject: FW: [xliff] best practice: should extraction process create targetelements?




From: "Doug Domeny" <ddomeny@ektron.com>
To: <xliff@lists.oasis-open.org>
Date: Mon, 13 Mar 2006 16:13:57 -0500














Not sure if this came through on the XLIFF
list or not. My apologies if this is a repeat.





Regards,

 

Doug Domeny

Software Analyst

 

Ektron, Inc.

+1 603 594-0249 x212

http://www.ektron.com

 











From: Rodolfo
M. Raya [mailto:rmraya@heartsome.net]

Sent: Thursday, March 09, 2006
12:44 PM

To: Doug Domeny

Cc: xliff@lists.oasis-open.org

Subject: Re: [xliff] best
practice: should extraction process create targetelements?





On Thu, 2006-03-09 at 10:16 -0500, Doug Domeny wrote:

Hi Doug,





Should the extraction process create a
target element with a copy of the source in it? 

1.      No,
the extraction process should only create the source tag. 



             
<trans-unit id="16" datatype="plaintext">

               
<source>Hospital Wide</source>

             
</trans-unit> 

1.      Yes,
but the target should be empty and the state=”needs-translation”. 



             
<trans-unit id="16" datatype="plaintext">

               
<source>Hospital Wide</source>

               
<target state="needs-translation"/>

             
</trans-unit> 

1.      Yes,
the target should be a copy of the source and the state=”needs-translation”. 



             
<trans-unit id="16" datatype="plaintext">

               
<source>Hospital Wide</source>

               
<target state="needs-translation">Hospital Wide</target>

             
</trans-unit>



There are formats that require creating a <target> element with text
different from the <source> at conversion time. For example:

·        

files are usually pre-translated. They can carry translations from Gettext or a
predefined empty target. 

·        
Trados Tagged RTF
files and TTX files present these cases: 

·        
Segments that have
fuzzy translation from Trados. The filter has to: 

·        
add the target text
from Trados in a <target> element 

·        
set the
"state" attribute of the new <target> to a suitable value 

·        
store the match
quality somewhere, in a <note> element for example 

·        
Segments that have a
100% match. The filter has to: 

·        
add the target text
from Trados in a <target> element 

·        
set the
"state" attribute of the new <target> to a suitable value 

·        
optionally, 
set the "approved" attribute of the <trans-unit> to
"yes" 



Could you please forward my message to the mailing list? Until yesterday I was
unable to post.


Best regards,

Rodolfo


 

  

  

   

    

    
--
The information in this e-mail is intended strictly for the addressee,
    without prejudices, as a confidential document. Should it reach you, not
    being the addressee, it is not to be made accessible to any other
    unauthorised person or copied, distributed or disclosed to any other third
    party as this would constitute an unlawful act under certain circumstances,
    unless prior approval is given for its transmission. The content of this
    e-mail is solely that of the sender and not necessarily that of Heartsome. 
    
   
  
  

  
 





















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

--

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