How to figure out what causes a "t3" folder to generate

[mdslup]

I am working on a pretty large manual, but everything is contained within the same folder as the root ditamap (with some subfolders).

As we worked on more content, a "t3" folder started appearing in the output with some of the same content as the root folder...I have encountered this in the past when something is linked outside the scope of the ditamap. Is there a way to figure out exactly why this t3 folder is appearing? I don't get any validation issues. Is there some scope or link tool I can run to see why it feels the need to create this extra folder?

[Radu]

Hi,

If you edit the transformation scenario you are using, in the Parameters tab you probably enabled the "fix.external.refs" parameter which is useful if you have references to resources outside of the DITA Map folder:
https://www.oxygenxml.com/doc/versions/ ... -refs.html

So that "t3" folder created by our pre-processing stage added to the publishing engine should usually contain resources which are outside of the DITA Map folder.

Regards,
Radu