Article View: adobe.scripting.indesign
Article #18831Re: Tables again
From: Ben Dupre
Date: Thu, 20 Feb 2003 16:26
Date: Thu, 20 Feb 2003 16:26
7 lines
1502 bytes
1502 bytes
You probably need other reasons to switch to XML. As Ole will also assert that tagged text is much more flexible. In our database catalog application, we started out thinking XML would do it all, but quickly ran into limitations that required us to use both scripting and XML. However, with the ammount of scripting needed to make the XML work for us, we really don't gain anything by using XML at all. Tagged text, on the other hand, we haven't tried, but I understand why it's better than XML. There is simply more built into the "schema" of ID tagged text. ID has a lot to improve on the XML side. I don't have the slightest idea though, what the next version will bring. Ben
Technical Details
Message-ID:
<1de7ed85.3@WebX.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news1.google.com!sn-xit-02!sn-xit-03!sn-xit-01!sn-xit-08!supernews.com!newsfeeds.sol.net!newsengine.sol.net!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!lnewspeer01.lnd.ops.eu.uu.net!emea.uu.net!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<1de7ed85.-1@WebX.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f939a,97cdbcf0601a13ef X-Google-Attributes: gidf939a,public X-Google-ArrivalTime: 2003-02-20 08:39:14 PST From: "Ben Dupre" <bdupre@sauer-danfoss.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news1.google.com!sn-xit-02!sn-xit-03!sn-xit-01!sn-xit-08!supernews.com!newsfeeds.sol.net!newsengine.sol.net!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!lnewspeer01.lnd.ops.eu.uu.net!emea.uu.net!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.scripting.indesign Subject: Re: Tables again Message-ID: <1de7ed85.3@WebX.la2eafNXanI> Date: Thu, 20 Feb 2003 08:26:32 -0800 References: <1de7ed85.-1@WebX.la2eafNXanI> Lines: 15 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit