Hi Ivan,
Here is an example. Open Arbortext Editor, do File > New, select the DocBook sample.
Position after <book>, and do Edit > Select Element Content.
To see Entities > Create File Entity from Selection, you need to enable Tools > Preferences > Window > Full menus.
Now, for some reason, in this case, I had trouble with Create File Entity from Selection. You may have to ask PTC support about that.
So I did a cut (control-X) of the content of the book element, and from the command line, did:
write -paste C:\temp\fragtest\docguts.xml
Then I did Insert > File Reference, and browsed to C:\temp\fragtest\docguts.xml. Voila.
Notice that the fragment starts with title. If you look at the innards of docguts.xml, it starts out like:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Fragment document type declaration subset:
Arbortext, Inc., 1988-2015, v.4002
<!DOCTYPE set PUBLIC "-//Arbortext//DTD DocBook XML V4.0//EN"
"axdocbook.dtd">
-->
<title>PTC Employs Its Own Arbortext® Software to Improve Delivery
It isn't really valid per any DTD/Schema; the DOCTYPE declaration is in a comment. So it's when you try to include it into your top-level document (into the DocBook book element, in this example) that it's content gets context checked for insertion into <book>.
Of course, you'll need to create 150 such fragment files, and do 150 Insert > File Reference operations into your top-level includer document. It would be possible to write ACL to help automate this, but I fear that would be beyond the scope of this forum. Perhaps others know of an easy or out of the box way to simplify the process for you.
Best regards,
Gary Grosso
Oberon Technologies Inc