Forum: SDL Trados support
Topic: Studio 2014 does not process DITA/XML files
Poster: Roy OConnor
Post title: It depends..
... I think, what the extension is. If the extension is DITA, then presumably DITA XML is what Studio expects, but if it finds an unexpected root element, say, then it may default back to XML. I have worked with Madcap Flare, for example, which uses the extension XML, but has a declaring URI in the header. I notice that the Studio DITA file type in my Studio 11 (not changed to 2014 yet) appears to contain some glossary tags, so the difference might not be due to the fact that the files are glossaries, but just that they have been produced differently.
If you compare the headers of the glossaries with those of the other files, you may be able to see what is different and modify the file type accordingly.
Also, what you could do, is to create an XML file type just for the glossaries. Choose the largest glossary which is most likely to contain most tags and use it as the rule file when creating a new file type. But you would still not be able to use the DITA extension.
Of course, you could always ask the client to tell you what they have done to the glossaries!
Good night!
Roy
Topic: Studio 2014 does not process DITA/XML files
Poster: Roy OConnor
Post title: It depends..
... I think, what the extension is. If the extension is DITA, then presumably DITA XML is what Studio expects, but if it finds an unexpected root element, say, then it may default back to XML. I have worked with Madcap Flare, for example, which uses the extension XML, but has a declaring URI in the header. I notice that the Studio DITA file type in my Studio 11 (not changed to 2014 yet) appears to contain some glossary tags, so the difference might not be due to the fact that the files are glossaries, but just that they have been produced differently.
If you compare the headers of the glossaries with those of the other files, you may be able to see what is different and modify the file type accordingly.
Also, what you could do, is to create an XML file type just for the glossaries. Choose the largest glossary which is most likely to contain most tags and use it as the rule file when creating a new file type. But you would still not be able to use the DITA extension.
Of course, you could always ask the client to tell you what they have done to the glossaries!
Good night!
Roy