[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Simplified XLIFF element tree
Yves, To my knowledge, no one has tried importing XLIFF with the added <mrk> elements. Perhaps it would work--that's encouraging. I use XSLT to process the <target> and suspected that a change in the markup could cause failure when matching inline target elements with their corresponding elements in the skeleton. Thanks for your input. Doug -----Original Message----- From: Yves Savourel [mailto:ysavourel@translate.com] Sent: Monday, August 23, 2010 8:37 AM To: 'xliff' Subject: RE: [xliff] Simplified XLIFF element tree Hi Doug, > However, if the XLIFF file comes back segmented, > it may not be able to perform the merge. That sounds strange to me. In all cases the translated file should have the same <trans-unit> elements as when you extracted it, even segmented, no? So the worst case would be that you have <mrk> elements in <target>, which could be segment markers or anything else. Or are you getting back files that have different <trans-unit> elements? -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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]