Empty data fields are not displayed in Trados Studio / not included in translated XML file : this problem is not solved so far

Question

The problem is that empty data fields (white spaces or fields without text) in the source language XML file are not displayed in Trados Studio and thus are not included in target language XML file. These empty fields are important so that TYPO3 contains the corresponding element (a container), even if it has no name (e.g. header/text). Without these empty fields, the data structure is no longer correct and we cannot import the translated XML file.

Paul · Answer

Christine Reversac 
 I'd say this problem will only get resolved when you resolve it! 
 Who created your custom XML filetype for this XML? 
 Notwithstanding that I don't really follow the logic here: 
 Christine Reversac said: The problem is that empty data fields (white spaces or fields without text) in the source language XML file are not displayed in Trados Studio and thus are not included in target language XML file. 
 No matter whether the text is extracted for translation or not will not affect the presence of the same fields in the target file. Whitespaces are normally managed by the "Whitespace" settings in your XML filetype. All of these things are down to you configuring the filetype to give you what you need. 
 You have not provided anything to enable us to make a sensible suggestion to help here. Have you checked to see if the parser rules are there for the content you need? Have you checked your Whitespace settings and how they are controlled by the XML file itself (if at all)? 
 Can you provide a sample file, and your settings file? 
 More fundamentally... what version of Trados Studio are you using?

Paul · Answer

Christine Reversac

Christine Reversac said:
This problem has been mentionned months ago from another translator and wasn't solved so far in this community.

Well I would like to see this unsolved question?

Christine Reversac said:
I thought I provided an exemple :

<Basis><![CDATA [Text to be translated]]></Basis>
<Translation><! CDATA [ ] ]></Translation>

That is not an example. It's two elements within an example. For the next time, this would would be an example (I had to guess the rest as I don't have your file):

<?xml version="1.0" encoding="UTF-8"?>
<translations>
    <item>
        <Basis><![CDATA[Text to be translated]]></Basis>
        <Translation><![CDATA[Translated text goes here]]></Translation>
    </item>
    <!-- More translation items can be added here -->
    <item>
        <Basis><![CDATA[Another text to translate]]></Basis>
        <Translation><![CDATA[Another translated text]]></Translation>
    </item>
    <!-- ... and so on for each piece of text to be translated -->
</translations>

This is important because for all I know there could be more nesting involved, or "special rules" to deal with duplications etc. So answering your question helpfully is difficult without better context.

I really doubt this is a problem that cannot resolved by creating the correct filetype to solve the issue. Hence why I'd like to see the original question so I can go back and at least provide a solution. It may be that as this is a bilingual format you will struggle with 2019 as the obvious choice would be to use the Multilingual XML filetype from the appstore for this:

https://appstore.rws.com/Plugin/13

This has only been available since the Trados Studio 2021 version, but it would easily handle the example file I just shared and I'm pretty sure it would handle whatever your file is too. So I'm happy to look at this if you can provide a better example... might be helpful for the future.

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

Trados Studio > 1. Trados Studio

Empty data fields are not displayed in Trados Studio / not included in translated XML file : this problem is not solved so far