New XML File Type - Cannot choose DTD as Import Configuration File

Question

Hello, 
 I have a problem with a DTD file that I want to use as import configuration base for my new XML file type. So, what I am doing is the following: I set up a new file type for xml. On the second page "Import of XML configurations" (I am working with the german version, so I am not sure if I use the right terms in English) I do not choose the standard configuration option but I try to upload my DTD file for the import of configurations based on a (INI-, ANL-, XML-, XSD- , ITS-) DTD file. Trados even recognizes the file I want to select (since it is a DTD). But when uploading it, I get the error message "The File Format of the chosen Import File is invalid". With a XML or INI file, it is working fine. 
 Why does this happen? Can anyone help me, please :-) 
 Thanks in advance, 
 Christiane

Paul · Accepted Answer

Hi Christiane, 
 Although I provided you with an example that worked, I also found some that didn't work at all. So I asked the dev team to look at it and we do have a bug that needs to be resolved. However, you may well be able to fix this yourself to allow you to create a new filetype based on the DTD you have. 
 There were two problems that we found with the example files I found to test with. I haven't seen your files so I'm guessing again ;-) But this might help. 
 
 If the DTD has a DOCTYPE definition then try removing it 
 If there are tab characters in the file try removing these 
 There was one definition that we needed to remove <!ATTLIST REPORT security (high | medium | low ) "low" > So if you have one formatted like this it might also be causing a problem. I don't know why exactly, but worth checking if the file still won't import after dealing with the first two issues

I would try 1. first, and if that doesn't help try 2. and then start looking at the definitions themselves if it still won't import. I know this isn't great, but until we resolve it this information might help you handle your own DTD files. The offer still stands to review them if you can provide a copy. 
 
 Finally, I have attached the two DTD's in question. One called will work.dtd and the other called won't work.dtd so you can see what changes we made to allow this test dtd I found to work.

Paul · Answer

Hi Christiane, 
 Can you confirm what version of Studio you are using? This should have been fixed in Studio 2014. So for earlier versions the only option was to use Trados, create the ini file and then use the ini in Studio. 
 If you have Studio 2014 and still have a problem are you able to share the DTD you are using?

Paul · Answer

Hi Christiane, 
 Please try the attached.

Paul · Answer

Hello Victor, 
 Apologies for the delay, this was a tricky one for me but Vlad in our support team managed to figure out how to handle the file. He thinks that the issue is caused by the parameter entities which are not correctly read if they are referenced in the attribute field. Here&rsquo;s a short explanation of the story: 
 www.stylusstudio.com/.../d_dtd24.html. 
 The example from the link talks about parameter entities when defined in elements and this works in Studio. However, if you define the parameter entities for the attributes, the import fails. 
 In order to make the .dtd work, he converted it to an .xsd like this one: 
 https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/tranthis_2D00_2.0.xsd 
 You can use this XSD successfully. 
 To do the conversion Vlad used Stylus Studio X15 which you can find if you google it, but you may also be able to make use of a perl script like this: 
 
 We have reported the problem with the original dtd but perhaps these workarounds will be useful in the meantime. 
 Regards 
 Paul

Paul · Answer

Hello Victor, 
 The other more obvious workaround of course I tested this morning is to import the DTD to TagEditor to get your INI file and then import the INI into Studio. This works perfectly. 
 https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/Victors-DTD.ini 
 Regards 
 Paul

Paul · Answer

Hi Victor, 
 I also found a nice workaround using SDL Legit! which is a free application on the OpenExchange. So if you use this it will probably be the simplest solution to your problem: 
 
 Regards 
 Paul

Trados Studio > 1. Trados Studio

New XML File Type - Cannot choose DTD as Import Configuration File