🚀 go-pugleaf

Hi again;

Our group receives XML files that contain eng data for multiple widgets inside 1 standard component. Like....

      <component> <Widget>
            <name>My Thing</name>
            <phone>555-1212</phon>
            <description>Very short</description>
         </Widget>





<Widget>
      <name>Their Thing</name>
      <phone>429-4242</phone>
      <description>Also short</description>
   </Widget>

... 

      </component>




Unfortunately, the 3rd party SW ("MakeWidgets") only allows engs to write 1 para of Widget description - no tables, graphics, etc - and our Widgets get complicated. We've chatted with the SW company about this restriction but alas, "MakeWidgets" can't change anytime soon.

So our group is trying to split out Widgets separately, treat them as Frame read-only text insets, then interleave long description areas. Like....

      <ModifiedComponent>




<Widget IsTextInset="Yes">
      <name>My Thing</name>
      <phone>555-1212</phon>
      <description>Very short</description>
   </Widget>

<LongDescription BelongsTo="My Thing">      

Blah, blah
     

   </LongDescription>

<WidgetIsTextInset="Yes">
      <name>Their Thing</name>
      <phone>429-4242</phone>
      <description>Also short</description>
   </Widget>

<LongDescription BelongsTo="Their Thing">      

Blah, blah
      <GraphicHere/>
   </LongDescription>

...

      </ModifiedComponent>




The final system would allow "MakeWidgets" to write Widget XML while Frame would input Widget XML as read-only text insets so Engs or TWs can see (but not write) the data while they write better descriptions. In the long run, we also want the "LongDescriptions" to be dbased text insets so we can reuse them in other docs.

Last restriction. "MakeWidgets" can't see the "LongDescription" element so we need to fold everything back into a single file once we write the XML from inside Frame.

This project entails 2 tasks (that I can see):

      Break 1 component file into multiple text insets (or read 1 element in
      the component file as 1 text inset, similar to a conref).






      Interleave multiple files into 1 single file that Frame accepts as input.
      BTW, it's interesting that Frame is good at creating multiple output files,
      but not-so-good at accepting multiple files as input. But never mind.




Both tasks seem difficult to do, so I'm soliciting ideas and opinions. Also raucous laughter. ;)

Any ideas?

Thanks!

David Blyth (the UNIX and vi dinosaur)
Staff Technical Writer
QCT Division
QUALCOMM - Standard Disclaimers Apply

Only 149,999,950 more years of Ruling The Earth to go
---------------------------------------------------------------

PS. Yes, I know DITA can handle modules like this - but "MakeWidgets" doesn't accept DITA format. This is one reason why I don't like DITA - it's TW oriented and High Tech XML formats are eng driven. So either you don't use DITA or you swap formats - extremely hard to do - and track info in 2 places. Yuck!

Sorry Ann Rockley.