[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] Simplified XLIFF element tree
Hi Yves, Thank you for your reply. As always it is full of insight and wisdom. We indeed map <tm:te> elements to <group> and <tm:tu> to <trans-unit>. You can use a simple XSLT transformation to generate the resultant XLIFF file. It is a beautifully elegant solution based completely on Open Standards: 1. If the input format is not in XML convert it losslesly to XML 2. Use W3C ITS rules for the document type to identify translatable text and attributes as well as 'within text' and subflow elements 3. Use SRX to segment the text 4. Use xml:tm to seed the document with the xml:tm namespace 5. Generate the XLIFF file from the xml:tm version of the file 6. Use GMX/V for all metrics After translation you can reverse the steps. Recreation of the target file can also be done via XSLT. This provides a completely modular and open framework where you can access the data at any point. I have nothing against an optional <ext-trans> element for systems that do not pre-segment. In our use of XLIFF I could not countenance a change to the segmentation that has been generated. This is a fundamental point, that will be common for all systems that pre-segment text. We expect a translation for every <trans-unit>, allowing only merging within the bounds of a <group> element. I see no reason to change the way we use XLIFF, which is a fundamental part of our architecture and works EXTREMELY well. We use a very small and efficient subset of XLIFF, which is very much in keeping with our discussions. Best Regards, AZ On 24/08/2010 13:39, Yves Savourel wrote: > Hi Andrzej,all, > >> We use the<group> element to signify major >> element boundaries so as to be able to prevent >> attempts at merging<trans-unit> elements across >> such boundaries. > I don't know xml:tm very well, but looking at the specification and examples it would seems that files with xml:tm can work with other representations than<group>+<trans-unit>. It's just a matter of mapping<tm:te> to the extracted text and<tm:tu> to the segments, just like for XLIFF 1.2<tm:te> are mapped to<group> and<tm:tu> mapped to<trans-unit>. > > Cheers, > -ys > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > -- email - azydron@xtm-intl.com smail - c/o Mr. A.Zydron PO Box 2167 Gerrards Cross Bucks SL9 8XF United Kingdom Mobile +(44) 7966 477 181 FAX +(44) 1753 480 465 www - http://www.xtm-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.
begin:vcard fn;quoted-printable:Andrzej Zydro=C5=84 n;quoted-printable:Zydro=C5=84;Andrzej email;internet:azydron@xml-intl.com tel;work:+441494558106 tel;home:+441494532343 tel;cell:+447966477181 x-mozilla-html:FALSE version:2.1 end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]