Hans-Georg Reiss

Hans-Georg Reiss said:

I am not a XML programmer, but I reckon that there is a way to enter this dtd file into the row with the file types so that further XML files can be treated adequately. Is this assumption correct?

Sort of.  The dtd is only used to validate the correctness of the XML.  Ideally you would create a custom XML filetype for your file and then include your schema if it's important for you to have the xml validated against it:

https://docs.sdl.com/813470/534137/sdl-trados-studio-2021-sr1/xml-validation-page

If you don't have the dtd then just turn off the validation as you don't have anything to validate against:

I created a new XML filetype using your XML file to create the parser rules automatically... so I haven't made any changes to exclude stuff or handle anything in attributes but when I use this and the validation off I see this:

I also don't see where you get the ' replaced with a ".  Can you point me to exactly where I need to look?

Paul

Hans-Georg Reiss probably means that the attribute values are enclosed in double quotes in the translated document. They were enclosed in single quotes AND sometimes in double quotes in the original. Both is perfectly legal for XML and HTML as far as I know:

Original:

Translation:

After having a second look: The file with "E" at the end, which I thought was Studio's output, is NOT the translation of the other file, but has been transformed somehow. Incorrectly.

Original:

"E"-File:

There are a lot of unescaped characters in the element values of the source file which should have been escaped: <, >, ", '. That is with certaintly a source of problems.

I wish I would understand what's going on with these files, but unfortunately I don't have the time to look further.

Daniel

Paul

Hans-Georg Reiss probably means that the attribute values are enclosed in double quotes in the translated document. They were enclosed in single quotes AND sometimes in double quotes in the original. Both is perfectly legal for XML and HTML as far as I know:

Original:

Translation:

After having a second look: The file with "E" at the end, which I thought was Studio's output, is NOT the translation of the other file, but has been transformed somehow. Incorrectly.

Original:

"E"-File:

There are a lot of unescaped characters in the element values of the source file which should have been escaped: <, >, ", '. That is with certaintly a source of problems.

I wish I would understand what's going on with these files, but unfortunately I don't have the time to look further.

Daniel

Thank you Daniel answering me despite of your limited time. If you should have a timeslot later on, I'd highly like to furnish you with everything needed to finding an answer as this is quite essential to continuing with good relations with one of my major clients in these pandemic times.

Hans-Georg Reiss

Do I assume correctly that the first file (Theme_Stromversorgung SMPS_00003.xml) is the source file you get from your customer?

Daniel

That is correct

Hans-Georg Reiss

I noticed that all text seems to exist twice in the source file, once as unescaped HTML, and once escaped in the dataset nodes. I assume you are trying to translate the unescaped version? Why are there two versions of the same text. Why is one escaped and one is not?

Daniel