Custom bilingual XML with HTML embedded content

Hi Community,


I received a custom XML file, with HTML embedded content, with both the source and the target content in it.

Screenshot of XML code with HTML tags such as 'span' and 'li' not being processed correctly in Trados Studio.

Screenshot showing XML content with embedded HTML not recognized by Trados Studio, displaying tags like 'span' and 'li' as plain text.

I tried creating a custom file type in Studio, but despite selecting the 'HTML embedded content processor', the HTML code such as <span> and <li> 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



Generated Image Alt-Text
[edited by: Trados AI at 4:46 AM (GMT 0) on 5 Mar 2024]
emoji
Parents
  • 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:

    1. create a TM from the existing file
    2. 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 Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi there,

    and what is with the "Bilingual XML File Type 1.0.0.0"? I use it time to time. I know it is not supported and it had disappeared from Internet but it would be great for Studio.

Reply Children
No Data