Article View: adobe.scripting.indesign
Article #8518Re: XML Export encoding error
From: Louise_Broda
Date: Fri, 06 Oct 2006 18:28
Date: Fri, 06 Oct 2006 18:28
1 lines
1414 bytes
1414 bytes
Thanks, Andrew. I agree, why can't we troubleshoot these errors within the app instead of having to use an external source? That said, your answer enabled me to accomplish what I needed right now, which was an xml coded version of certain elements of text only. What I did was, using the Table of Contents utility, compiled the elements I needed by style, then exported that text as rtf, imported that into a new document, loaded my xml tags, mapped styles to tags, exported as xml. Tested by importing the xml into a template that contained the correct styles, mapped the styles back to the tags, and placed the single story that had been generated. It's not perfect, but at least it gives us a starting point.
Technical Details
Message-ID:
<3bc1de9f.1@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!newsfeed.x-privat.org!spool.x-privat.org!webcrossingReferences:
<3bc1de9f.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: f939a,e2a1abc7af8b962b X-Google-Attributes: gidf939a,public X-Google-Language: ENGLISH,ASCII-7-bit From: Louise_Broda@adobeforums.com Newsgroups: adobe.scripting.indesign Subject: Re: XML Export encoding error Message-ID: <3bc1de9f.1@webcrossing.la2eafNXanI> Date: Fri, 6 Oct 2006 11:28:48 -0700 References: <3bc1de9f.-1@webcrossing.la2eafNXanI> Lines: 10 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!newsfeed.x-privat.org!spool.x-privat.org!webcrossing