SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
Hi there fellow Trados Studio users and SDL staff,
One of our customers has sent us an XML file they were given by an external agency that contains the text to appear in an interactive infographic.
Unfortunately, when loaded into Trados, the file appears completely empty. I'm pretty sure the problem lies with the XML, and perhaps a lack of "closing tags"?
None of the text to be translated shows up in black in Notepad++ either
Here's an excerpt:
Is there anything I can do to make it translatable? A quickish find and replace operation to add in closing tags perhaps?
Something tells me the entry target="" could perhaps be intended for the translation as it appears after each and every section of translation-relevant text.
Any pointers would be much appreciated!
Andrew James Wood
This article may be better for you as it's more relevant to how to use the tool to handle an XML file:
It's pretty straightforward…
A few things...
I think you need to have a discussion with your client, ask them what's supposed to be translated and where the translatable text needs to be. All easy to handle, but you should not be guessing.
When creating the custom XML filetype, am I right in thinking it's the parser rules that I use to tell Trados to treat the "description" and "title" attributes as markers for translatable text? I've had a play around with it a little, but can't get Trados to recognise any text. I've had a brief look through the w3schools training stuff on XML, but I'm a bit lost, to be honest.
It is just the stuff marked with "description" and "title" that needs to be translated. The customer is talking about manually copying and pasting over the German with English, but there must be a better solution. All their other translators have just sent the file back to them in a kind of "computer says no" fashion.
It's pretty straightforward and if you provided a snippet of the file instead of a screenshot I could show you a better example of how to do this with your file. But here's a quick example based on this snippet I created from the information you have shared:
<?xml version="1.0" encoding="UTF-8"?>
<hotspot skinid="ht_node" pan="262.71" title="Maschinekabinen" id="point28" tilt="11.23" description="Hier wird die Beschreibung eines Maschinenraums stehen." />
<hotspot skinid="ht_node" pan="226.86" title="Motorenblock" id="point29" tilt="10.95" description="Der Motorblock unterstützt die im Maschinenraum auftretenden Kräfte." />
I used XML2 when I created the new XML filetype and I based this on using XPath rules as I prefer the flexibility this offers. I then created three rules:
//* (to tell Studio not to extract anything at all)
//hotspot/@description (to extract text from the description attribute inside the hotspot element)
//hotspot/@title (to extract text from the title attribute inside the hotspot element)
The sample file I created now parses like this:
Andrew James Wood said:All their other translators have just sent the file back to them in a kind of "computer says no" fashion.
They either don't have Trados Studio or they don't know how to use it :-)
Once again, Paul rides to the rescue!
I'll definitely study that article of yours, Paul, but having added those XPath rules to the custom XML filetype I'd created, Studio has picked up all the text beautifully.
To be honest, I suspect that the vast majority of Trados users don't have the faintest clue about this side of the software or the slightest intention of grappling with what many would perceive as something well beyond their remit that requires skills and knowledge they don't have and aren't interested in.
I'm just pig-headed and stubborn
Many, many thanks indeed for your assistance and explanations - over the years, I'm very slowly expanding my horizons!