Hi G廨ard and Yves,
Please find attached a sample TBX file which covers the single term "alternating
current" for English and Spanish. A judicious review of the contents should
result in the following observations:
1) That TBX is an excellent format for the exchange of terminology data.
2) That TBX is most probably not such a good fit for the inline embedding of
terminology in XLIFF <target> elements.
One way of using TBX with XLIFF would be to use the term reference ID to enable
accessing the term in a parallel attached TBX file e.g. using the tbx-example
file attached:
<trans-unit id="1.0">
<source>The motor needs 240V Alternating Current to operate</source>
<target>The motor needs 240V <mrk mtype="term" ext:pos="NN"
ext:tgt="e2800372684057780651">Alternating Current</mrk> to operate</target>
</trans-unit>
The key "e2800372684057780651" would then be used to locate the terminology data
in the TBX document. The TBX document would have to accompany the XLIFF file in
one form or another. Although this would be workable, it would for my purposes
fall into the category of overkill.
I am very grateful to Yves for his suggestion, which meet my requirements
completely. For my application the proposes the <mrk> mechanism will be ideal.
Best Regards,
AZ
Yves Savourel wrote:
> Agreed.
>
> -----Original Message-----
> From: Gerard Cattin des Bois [mailto:]
> Sent: Thursday, April 15, 2004 2:27 PM
> To: Yves Savourel
> Cc: XLIFF Main List
> Subject: RE: [xliff] Adding inline terminology information to XLIFF
>
> Yes I meant TBX terminology data representation into Xliff. We may want to
> take a look into this issue to see if we have a good fit.
>
> Cheers,
> -G廨ard
> Families are living sanctuaries
>
>
> -----Original Message-----
> From: Yves Savourel [mailto:]
> Sent: Thursday, April 15, 2004 1:17 PM
> To: Gerard Cattin des Bois
> Cc: XLIFF Main List
> Subject: RE: [xliff] Adding inline terminology information to XLIFF
>
> I'm not sure what you mean:
> - TBX formatted data in XLIFF?
> - XLIFF in TBX?
> - if you mean "how TBX terminological info can get into <mrk>?", I guess one
> could have a mapping between TBX entries and extended attributes in the <mrk
> mtype="term"> element.
>
> I'm afraid I don't know TBX enough to contribute to an intelligente answer.
>
> Cheers
> -yves
>
> -----Original Message-----
> From: Gerard Cattin des Bois [mailto:]
> Sent: Thursday, April 15, 2004 2:06 PM
> To: Yves Savourel; XLIFF Main List
> Subject: RE: [xliff] Adding inline terminology information to XLIFF
>
> Yves, how does this play with tbx formatted data?
>
> Cheers,
> -G廨ard
> Families are living sanctuaries
>
>
> -----Original Message-----
> From: Yves Savourel [mailto:]
> Sent: Thursday, April 15, 2004 12:38 PM
> To: XLIFF Main List
> 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:]
> Sent: Monday, April 12, 2004 1:16 PM
> To:
> 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 -
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.
