Skip to main content
1-Visitor
June 19, 2015
Question

Print Compose multiple XML files into one PDF?

  • June 19, 2015
  • 1 reply
  • 6496 views

Fellow Forum Members,

Is it possible in Arbortext Editor 6.1 to use the Print Compose feature for the task of printing 150 separate XML files into a single PDF in a batch mode process? The idea I have is to code a XML file that will list all of the XML files in the order I want and here is where I need help. How can I direct the Print Compose tool to print all of the XML files in a batch mode by using such a XML list file?  Any opinion on how I can accomplish this will be greatly appreciated.  Thanks in advance.

1 reply

1-Visitor
June 19, 2015

Hi Ivan,

This sounds like the sort of thing which is typically handled by creating a top-level XML file which references the 150 other files via XML Include or file references. This requires that the top-level tag in your included files is allowed (in context) within some tag in your including document. This may require a small amount of DTD/XML Schema work. Or the 150 files could be saved as fragments with their top-level tag removed. One way to create such fragments is to select everything except the top-level tag and Select Entities > Create File Entity from Selection.

Is this along the right lines, or did I misunderstand your situation?

Best regards,

Gary Grosso

Oberon Technologies Inc

it11-VisitorAuthor
1-Visitor
June 19, 2015

Gary and Jeff,

Thanks for the two great postings.  I have continued researching this problem and have narrowed it down to what is known as a "WRAPPER FILE". Which is pretty much what both of you are describing in your postings.  A wrapper file is hard coded in XML and inside of it one needs to code all 150 xml files in a list as references that reflects the order you want your 150 XML files to output in as a PDF.  Gary I think I follow with what you mention about selecting all tags (except to level tag) and then selecting the  "Create File Entity from Selection" menu item in Arbortext. However, I hope you can clarify whether or not if it is still necessary for me to tweak the S1000D 4.01 Schema I'm using  if I change all 150 of my XML files over to becoming Entities?  It would be cool if I can avoid tweaking the Schema. Also once I have 150 entities created how do I wrap them so that Arbortext Print Compose sees all of the 150 entities as a single consolidated XML file that needs to be converted into a single PDF in a single print operation? 

If anyone out there can please expand on how to code a WRAPPER file by posting some actual XML coding examples it will be much appreciated. Also examples on how to get it to work by relying in using Entities will be much appreciated.  In short, any help will be tremendously appreciated because I need help.  Thanks in advance.

it11-VisitorAuthor
1-Visitor
June 22, 2015

Gareth,

Thank you very much for your post.  You are correct in pointing out S1000D supports a type of data module called a " Publication Data Module" which is what I am in turn referring to as a "WRAPPER FILE".  And yes what I am trying to do is aggregate all of my data modules into a single XML file which I can then feed to the Print Composer option in my Arbortext Editor.  The big problem is the Print Compose feature in Arbortext Editor seems to totally reject the "Publication Module.xml " file I have coded. It seems to be blind to the entire wrapper file and only outputs a single page which is the front cover as a PDF file.

Does anyone out there know what code I need to add to my Publication Module.xml " file so that the Print Compose feature in my Arbortext Editor accepts it and processes all of the XML files into a single PDF using the Army provided XSLT stylesheet I define. 

Below is some sample code from an actual S1000D Publication Data Module. It's from an example manual that is public information. Please note, it only contains references to three XML files identified by the opening tag "<dmRef id="dm-000">".  I would like to know what code I need to add to the code below so that Arbortext Editor Print Composer does not reject it and outputs a PDF of all dmrefs listed in the code. Any help will be greatly appreciated.

<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" href="pm4-0.xsl"?>

<?altova_xslfo FO-3031-A00-USARMY-MAIN_001-00_EN-US.xsl?>

<pm xmlns:dc="http://www.purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.s1000d.org/S1000D_4-0/xml_schema_flat/pm.xsd">

  <rdf:Description>

  <dc:title>Phun Gun Operator and Field Maintenance Manual</dc:title>

  <dc:creator>07GB6</dc:creator>

  <dc:subject>Phun Gun</dc:subject>

  <dc:identifier>TM 9-1005-666-13</dc:identifier>

  <dc:language>en-US</dc:language>

  </rdf:Description>

  <identAndStatusSection>

  <pmAddress>

  <pmIdent>

  <pmCode modelIdentCode="S1000DGUN" pmIssuer="91005" pmNumber="MM301" pmVolume="00"/>

  <language countryIsoCode="US" languageIsoCode="en"/>

  <issueInfo inWork="00" issueNumber="001"/>

  </pmIdent>

  <pmAddressItems>

  <issueDate day="15" month="09" year="2011"/>

  <pmTitle>Operator &amp; Field Maintenance Manual</pmTitle>

  <shortPmTitle>Phun Gun 30D (NSN 4940-00-017-0000) (EIC OOH)</shortPmTitle>

  </pmAddressItems>

  </pmAddress>

  <pmStatus issueType="new">

  <security securityClassification="01"/>

  <dataRestrictions>

  <restrictionInstructions>

  <dataDistribution>DISTRIBUTION STATEMENT A:  Approved for public release; distribution is unlimited.</dataDistribution>

  <exportControl>

  <exportRegistrationStmt>

  <simplePara>WARNING: Export control statement here.</simplePara>

  </exportRegistrationStmt>

  </exportControl>

  <dataDestruction>DESTRUCTION NOTICE: Destroy by any means possible to prevent disclosure of contents or reconstruction of the document.</dataDestruction>

  </restrictionInstructions>

  <restrictionInfo>

  <policyStatement>Classification source and reason for classification of this publication per DODI 5200.001-R.</policyStatement>

  </restrictionInfo>

  </dataRestrictions>

  <responsiblePartnerCompany>

  <enterpriseName>HEADQUARTERS, DEPARTMENT OF THE ARMY</enterpriseName>

  </responsiblePartnerCompany>

  <originator enterpriseCode="1L6T4">

  <enterpriseName>US Army Materiel Command (AMC) Logistics Support Activity (LOGSA)</enterpriseName>

  </originator>

  <applic>

  <displayText/>

  </applic>

  <pubMedia pubMediaCode="PDF" pubMediaType="PDF - Optimized for Standard page size"/>

  <qualityAssurance>

  <firstVerification verificationType="tabtop"/>

  </qualityAssurance>

  <remarks>

  <simplePara>General purpose notices may appear here.</simplePara>

  </remarks>

  </pmStatus>

  </identAndStatusSection>

  <content>

  <pmEntry pmEntryType="pmt51">

  <dmRef id="dm-0001">

  <dmRefIdent>

  <dmCode modelIdentCode="S1000DGUN" systemDiffCode="0" systemCode="00" subSystemCode="0" subSubSystemCode="0" assyCode="00" disassyCode="00" disassyCodeVariant="A" infoCode="012" infoCodeVariant="J" itemLocationCode="A"/>

  <issueInfo inWork="00" issueNumber="001"/>

  </dmRefIdent>

  <dmRefAddressItems>

  <dmTitle>

  <techName>Phun Gun</techName>

  <infoName>Safety summary</infoName>

  </dmTitle>

  </dmRefAddressItems>

  </dmRef>

  <dmRef id="dm-0002">

  <dmRefIdent>

  <dmCode modelIdentCode="S1000DGUN" systemDiffCode="0" systemCode="00" subSystemCode="0" subSubSystemCode="0" assyCode="00" disassyCode="00" disassyCodeVariant="A" infoCode="00S" infoCodeVariant="A" itemLocationCode="A"/>

  <issueInfo inWork="00" issueNumber="001"/>

  </dmRefIdent>

  <dmRefAddressItems>

  <dmTitle>

  <techName>Phun Gun</techName>

  <infoName>List of effective data modules</infoName>

  </dmTitle>

  </dmRefAddressItems>

  </dmRef>

  <dmRef id="dm-0003">

  <dmRefIdent>

  <dmCode modelIdentCode="S1000DGUN" systemDiffCode="0" systemCode="00" subSystemCode="0" subSubSystemCode="0" assyCode="00" disassyCode="00" disassyCodeVariant="A" infoCode="001" infoCodeVariant="A" itemLocationCode="A"/>

  <issueInfo inWork="00" issueNumber="001"/>

  </dmRefIdent>

  <dmRefAddressItems>

  <dmTitle>

  <techName>Phun Gun</techName>

  <infoName>Title page</infoName>

  </dmTitle>

  </dmRefAddressItems>

  </dmRef>

  </pmEntry>

  </content>

</pm>