[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Segmentation proposals for the main XLIFF TC
Hi Everyone, With regard to last Tuesday's meeting, I would like to propose that we are ready to submit the following points to the main XLIFF committee: 1) The following two extra attribute values are required to enable a translator to indicate that the target trans-unit is not a direct translation of the source: 1.1) "not-equivalent" - this attribute value indicates that the target text should not be loaded into any leveraged memory database. This can occur if the source relates to market specific details that are not relevant regarding leveraged memory. 1.2) "merged" - this attribute value indicates that the target text relates to one or more trans-unit source text elements. This can happen when the source text has been segmented in such a way that a translation of the individual elements is impossible without recourse to a "merged" translation against the head element. In such an instance the text for the encompassed target elements must be empty to indicate that the translation is merged with the head element. The next non empty target element indicates the end of the run of "merged" elements. 2) We have established that a perfectly viable way of handling segmentation through the means of treating an XLIFF file as a normal XML file. The XLIFF file target elements, which at the time contain the source text, can have segmentation information added by means of a segmentation namespace such as xml:tm using SRX rules. A normal XML XLIFF extraction can then be executed on the file using either an XSLT transformation, or program. The resultant skeleton file will enable the translated text to be merged with the original XLIFF document. An XSLT transformation can then be used to strip out the segmentation namespace, resulting in a "translated" original unsegmented XLIFF file. This solution is ideal for a production process that can handle pipeline transformations. It is not necessarily suited to interactive segmentation that is being executed within a user interface centered environment. The XLIFF segmentation sub-committee will continue trying to reach a solution for that type of environment. I have provided examples for point 2) that show individual stages of the process. We may need to rework some of the wording of the points. Best Regards, AZ -- email - azydron@xml-intl.com smail - c/o Mr. A.Zydron PO Box 2167 Gerrards Cross, Bucks SL9 8XF 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]