[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Adding inline terminology information to XLIFF
Hi Andrzej, I believe there is a mechanism in XLIFF that allows you to tag terms in the source and target text: The <mrk> element has a mtype attribute that can take values from ISO-12620 2.1.11, one of them is "term". As <mrk> also allows extensions, one could easily add additional information as needed. Your example could be tagged as follow: <trans-unit id="1.0"> <source>Remove the left-handed widget from the subassembly</source> <target><mrk mtype="term" ext:pos="VB" ext:tgt="odlacz">Remove</mrk> <mrk mtype="term" ext:pos="NN" ext:tgt="leworeczna lydzetka">the left-handed widget</mrk> from <mrk mtype="term" ext:pos="NN" ext:tgt="podzespol">subassembly</mrk></target> </trans-unit> Maybe a common set of extended attribute for terminology may be created and used by everyone. That goes back to the idea of developing a library of extensions for various specific purpose. Hope this helps. Cheers, -yves -----Original Message----- From: Andrzej Zydron [mailto:firstname.lastname@example.org] Sent: Monday, April 12, 2004 1:16 PM To: email@example.com Subject: [xliff] Adding inline terminology information to XLIFF LIGHTWEIGHT REQUEST FOR COMMENT Date Submitted: 04 / 15 / 2004 Author(s), Contributor(s) with affiliation(s): Andrzej Zydron 1. STATEMENT OF PURPOSE The ability to include terminology information in XLIFF files. 2. STATEMENT OF REQUIREMENTS We have a requirement to include terminology information embedded in the <target> elements of XLIFF files. 3. PROPOSAL We would like to include identified target terminology information within XLIFF <target> elements - e.g. <trans-unit id="1.0"> <source>Remove the left-handed widget from the subassembly</source> <target><term pos="VB" tgt="odlacz">Remove</term> <term pos="NN" tgt="leworeczna lydzetka">the left-handed widget</term> from <term pos="NN" tgt="podzespol">subassembly</term></target> </trans-unit> 4. IMPLEMENTATION Either create a new <term> element that is a child of <target> or allow namespace extensions within <term>. 5. SCHEMA/DTD Either create a new <term> element that is a child of <target> or allow namespace extensions within <term>. 6. BACKWARDS COMPATIBILITY No effect on backwards compatibility. Regards, Andrzej Zydron -- email - firstname.lastname@example.org 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. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xliff/members/leave_workgroup.p hp.