Article View: adobe.framemaker.sgml
Article #164Re: Making a valid XML DTD out of a more general EDD?
From: Van_Kurtz
Date: Fri, 30 Jan 2009 16:27
Date: Fri, 30 Jan 2009 16:27
14 lines
1792 bytes
1792 bytes
Harald, You write: For another customer, I may have a need to "interface" with xml databases to get some content into an FM file. I had the project of creating an XSLT that converted an XML file generated by a manufacturing database, that listed the parts and subparts of the product. The person who created the XML file devised his own set of elements and attributes. I then had to create the translation to get the content into our Frame structure for a parts catalog. It was not difficult. It took a few weeks of learning XSLT, but it was straightforward. The resulting text file was only two pages. The XSLT file is applied when you open the XML file from within Frame. This is set up in a structapp. The only additional thing needed was a read/write file that translated the table elements into Frame tables and told Frame how to divide the XML file into individual document files, that chapters of a book. The read/write file was less than 10 lines long. Note that if you apply the XSLT outside Frame using another application, you still need a read/write file to convert the table elements correctly. So, from my experience, you can do it all using Frame. Good luck, Van
Technical Details
Message-ID:
<59b686a8.12@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newshub.sdsu.edu!webcrossingReferences:
<59b686a8.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fcc08,7b6fc3c63283a48a X-Google-Attributes: gidfcc08,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Van_Kurtz@adobeforums.com Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newshub.sdsu.edu!webcrossing Newsgroups: adobe.framemaker.sgml Subject: Re: Making a valid XML DTD out of a more general EDD? Message-ID: <59b686a8.12@webcrossing.la2eafNXanI> Date: Fri, 30 Jan 2009 08:27:54 -0800 References: <59b686a8.-1@webcrossing.la2eafNXanI> Lines: 27 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit