Re: [xliff] Adding inline terminology information to XLIFF

Hi John,

Thanks for your comments. Mine and Kara's requirements are very similar. I 
remember Kara raising the issue in Washington. For me Yves solution would work 
without any problems.

My trans-units are already at a sentence level of granularity. For unmatched 
trans-units (where there are no update or leveraged matches) I do a part of 
speech analysis and identify noun phrases in order to look up target language 
terminology so that I can provide the translator with approved terminology. This 
improves the quality of the translated material considerably and makes the 
translator's job much easier.

Best Regards,

AZ

John Reid wrote:
> In our face-to-face, Kara Warburton raised a similar issue regarding the 
> overloading of <mrk> 
> (http://www.oasis-open.org/archives/xliff/200312/msg00015.html).  She 
> pointed out that TBX could not be embedded there because of the lack of 
> support for extensions within those elements. She suggested that there 
> be both a <mrk> and <term> element within <source> and <target>. 
> Andrzej's proposal is in line with those suggestions.
>  
> Maybe allowing extensions within the <source> and <target> would 
> overcome this issue as well as some others we are grappling with. 
>  
> What do you think? Do you recall our argument against allowing 
> extensions within those elements?
>  
> Regards,
> john

-- 


email - 
smail - Mr. A.Zydron
         24 Maybrook Gardens,
         High Wycombe,
         Bucks HP13 6PJ
Mobile +(44) 7966 477181
FAX    +(44) 870 831 8868
www - http://www.xml-intl.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
may not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version. Unless
explicitly stated otherwise this message is provided for informational
purposes only and should not be construed as a solicitation or offer.