hi again;<br /><br />our group receives xml files contain eng data multiple widgets inside 1 standard component. like....<br /><br /> <pre><br /> <component><br /> <widget><br /> <name>my thing</name><br /> <phone>555-1212</phon><br /> <description>very short</description><br /> </widget><br /><br /> <widget><br /> <name>their thing</name><br /> <phone>429-4242</phone><br /> <description>also short</description><br /> </widget><br /> ...<br /> </component><br /> </pre><br />unfortunately, 3rd party sw ("makewidgets") allows engs write 1 para of widget description - no tables, graphics, etc - , our widgets complicated. we've chatted sw company restriction alas, "makewidgets" can't change anytime soon.<br /><br />so our group trying split out widgets separately, treat them frame read-only text insets, interleave long description areas. like....<br /><br /><pre><br /> <modifiedcomponent><br /> <widget istextinset="yes"><br /> <name>my thing</name><br /> <phone>555-1212</phon><br /> <description>very short</description><br /> </widget><br /><br /> <longdescription belongsto="my thing"><br /> blah, blah<p/><br /> <table/><br /> </longdescription><br /><br /> <widgetistextinset="yes"><br /> <name>their thing</name><br /> <phone>429-4242</phone><br /> <description>also short</description><br /> </widget><br /> <br /> <longdescription belongsto="their thing"><br /> blah, blah<p/><br /> <graphichere/><br /> </longdescription><br /> ...<br /><br /> </modifiedcomponent><br /></pre><br />the final system allows "makewidgets" write widget xml while frame inputs widget xml as<br />b read-only<br />text insets engs or tws can see (but not write) data while create better descriptions. in long run, want "longdescriptions" dbased text insets can reuse them in other docs.<br /><br />last restriction. "makewidgets" can't see "longdescription" element need fold single file once write xml inside frame. project entails 2 tasks (that see):<br /><ul><br /><li>break 1 component file multiple text insets (or read 1 element<br />in component file 1 text inset, similar conref).</li><br /><br /><li>interleave multiple files 1 single file frame accepts input. btw, it's interesting frame @ creating multiple output files, not-so-good @ accepting multiple files input. never mind.</li><br /></ul><br />both tasks seem difficult do, i'm soliciting ideas , opinions. raucous laughter. ;)<br /><br />any ideas?<br /><br />thanks!<br /><br />---------------------------------------------------------------<br />footnote. yes, know dita can handle modules - "makewidgets" doesn't accept dita format. 1 reason why don't dita - it's tw oriented , high tech xml formats eng driven. either don't use dita or swap formats - extremely hard - , track info in 2 places. yuck!<br /><br />sorry ann rockley.<br />---------------------------------------------------------------<br /><br />david blyth (the unix , vi dinosaur)<br />staff technical writer<br />qct division<br />qualcomm - standard disclaimers apply<br /><br />only 149,999,950 more years of ruling earth go<br />---------------------------------------------------------------
hi david...
yuck.
i think you're looking @ complex xslt import/export process and/or custom plugin development.
so .. you're trying insert each "widget" data model of own acts container each basic widget description plus more verbose description. you're not trying stuff additional data base makewidget model, right?
i may dita-focused, think little (or lot) of work, dita. dita's specialization feature lets create data model uses element names of choosing long falls structure dita supports. makewidget model looks pretty basic , should fit existing dita construct.
you define container model (using base dita elements or specialization), , pull in each widget conref. doing wouldn't need separate or merge .. conreffed widgets show inline within uber description, while remaining intact within original makewidgets file. need able add "id" attribute each widget top level component element .. possible?
or .. maybe i'm crazy. :)
...scott
scott prentice
leximation, inc.
www.leximation.com
yuck.
i think you're looking @ complex xslt import/export process and/or custom plugin development.
so .. you're trying insert each "widget" data model of own acts container each basic widget description plus more verbose description. you're not trying stuff additional data base makewidget model, right?
i may dita-focused, think little (or lot) of work, dita. dita's specialization feature lets create data model uses element names of choosing long falls structure dita supports. makewidget model looks pretty basic , should fit existing dita construct.
you define container model (using base dita elements or specialization), , pull in each widget conref. doing wouldn't need separate or merge .. conreffed widgets show inline within uber description, while remaining intact within original makewidgets file. need able add "id" attribute each widget top level component element .. possible?
or .. maybe i'm crazy. :)
...scott
scott prentice
leximation, inc.
www.leximation.com
More discussions in FrameMaker Structured
adobe
Comments
Post a Comment