Custom bilingual XML with HTML embedded content

Question

Hi Community, I received a custom XML file, with HTML embedded content, with both the source and the target content in it. I tried creating a custom file type in Studio, but despite selecting the 'HTML embedded content processor', the HTML code such as and

is not picked up and processed by Studio. Also both the source content and the translation should be imported into the file, so the translation can be reviewed in Studio. I am not quite sure where to start. Please find below a sample file and the custom file type, as far as I got: XML file.zip Can you please help me, pointing me to the right direction? Thank you!! Greta

Paul · Accepted Answer

Greta Magyar 
 Studio doesn't support BilingualXML so you can only handle this using a monolingual XML filetype as you have attempted to create. But this is going to be useless to you unless you can copy the source into the target and translate the target, then add a TM (perhaps) that contains the current translations. So if you have to use Studio for this your course of action would be this: 
 
 create a TM from the existing file 
 manipulate the XML to get the source into the target element 
 
 To do the first I try this perhaps... extract the source with a custom XML filetype and export to Excel (appstore). Then extract the target (change filetype settings to pull the target) and export to Excel. Merge the two Excel files into one and convert the Excel to a TM (Glossary Converter perhaps... many ways to do this). 
 Then using a text editor that supports regex you replace the target content with the source. Then Open the XML again, using the target extraction in your custom filetype (this will now contain the source content), pretranslate from your TM and review. 
 Finally save the target file and you have a reviewed target. 
 A bit messy... if your client has a developer I'd recommend creating a bilingual XML filetype to handle this, especially if they get a lot of these files. The SDK contains an example of how to do this and I know several companies who have done it, but none of them have put their solutions on the appstore I'm afraid. 
 Maybe someone has a better idea... that would be my approach if I was unable to develop a filetype for this. Sometimes I think the cost of employing a developer to create filetypes when you need them would pay for itself over and over again. Studio is great for custom solutions if you have a developer!

Paul · Answer

Greta Magyar Juraj Baran 
 This new filetype for 2021 SR2 may be a good solution for you: 
 https://community.rws.com/product-groups/translationproductivity/w/customer-experience/6039/multilingual-xml-filetype

Daniel Hug · Answer

Hi Víctor Falcó , 
 I don't know whether my approach is universally applicable, but here is how I do it. 
 I usually apply this to short texts from a CMS. In this CMS, each field (page title, meta description ...) will be in a separate XML element, so I know that a certain element in the source language corresponds to a certain element in the target language. 
 Example 
 Field "page title": 
 EN: "Our best product" 
 DE: "Unser bestes Produkt" 
 
 Using Regex and a program called PowerGREP (you can do this with any scripting language as well) I split the bilingual file into a source and a target language file per field, so I'd come out with a list of files like: 
 Folder "EN": 
 001-soandsopage-pagetitle.xml 002-soandsopage-metadescription.xml 
 .... 
 
 Folder "DE": 
 001-soandsopage-pagetitle.xml 002-soandsopage-metadescription.xml 
 .... 
 Using Okapi, I do a sentence alignment for each of these files. The outcome is a list of XLF files, one per file pair. 
 Those files I translate in Trados Studio. 
 Then I use Okapi to convert the translated XLF files back to XML, merge the XML files into one and upload. 
 That's the outline. Hope it helps. 
 Daniel 
 
 Do give the Multilingual XML filter a try, it has quite an ingenious way of handling bilingual alignment which is more manual, but also more robust than my method.

Víctor Falcó · Answer

Thank you, Daniel Hug ! 
 An interesting approach, although I'd say it's even a bit more laborious than the one I have managed to come up with. 
 My source file = "lazy xliff" (bilingual xliff from WordPress, already pretranslated, big chunks of code within CDATA elements). Built-in Trados xliff filetype delivered bad segmentation (paragraph-level) and some tag issues. Multilingual xml filetype delivers nice segmentation and tag handling, but alignment issues. So, using multilingual xml file type, here's my workaround: 
 
 Process source xliff/xml file [a]. 
 Copy text to target (all segments) 
 Rename source xliff/xml file [b] and process it again, but in reverse (mapping xml target element as the source lang.) 
 Export [a] & [b] as Word (I use SDL XLIFF Converter) 
 In Word, merge the exported [a]+[b] files (by copying either source or target column of [b] to target column of [a]) 
 Import merged Word file back to Trados, into file [a]. 
 
 BEFORE: 
 
 AFTER: 
 
 Hope it helps and please feel free to suggest any improvement ideas.

Trados Studio > 5. Regex and XPath

Custom bilingual XML with HTML embedded content

Top Replies