Re: Getting data out of QuarkXpress (4.x)
Re: Getting data out of QuarkXpress (4.x)
- Subject: Re: Getting data out of QuarkXpress (4.x)
- From: Simon Forster <email@hidden>
- Date: Tue, 5 Aug 2003 11:30:06 +0100
Many thanks to all who replied to my original posting (see below
signature).
Effectively, there were 2 responses: use Xcatalog and assign names to
text boxes to identify the data.
Xcatalog <
http://www.emsoftware.com/products/xcatalog>
Looks like a useful product. However, this seems to be targeted at the
"Price List" type market. By this I mean people who produce the same
(or similar) brochure or catalog on a regular basis and need to update
this from data held in a database application. My requirement is to
produce a brochure of one-off travel and course data. This brochure
will go through the proofing cycle at the end of which its data will be
the up-to-date stuff. We then need to extract the data from Quark and
stick it back in the database. i.e. once out and then once back in.
Xcatalog doesn't seemed to be designed for this.
Named Text Boxes
Looking good. This will allow me to identify blocks of data but is
quite coarse grained. Xcatalog makes use of invisible tags to mark up
data in text boxes. Can someone tell me more about these?
Rather than pepper the list with silly questions, what book would you
recommend for scripting QuarkXpress?
TIA
Simon Forster
____________________________________________
LDML Ltd, 28 Montgomery Road, London, W4 5LZ, UK
Tel: +44 (0)70 9230 5244 Fax: +44 (0)70 9230 5247
____________________________________________
We've got some structured data which is being used to set a Quark doc.
While I haven't really scripted Quark in anger, I doubt there will be
a big problem getting the data into Quark (I can always go and buy a
book or two :-). My concern is getting the data out again in a
structured fashion. How do we maintain a sense of the data's original
structure so that we can suck text out of Quark and drop it back into
a database.
OK. In a little more detail:
We've got a database of circa 100 tours. These tours have a title,
tour director, description, itinerary, cost, etc. When we're ready, we
export this data to QuarkXpress for setting as a brochure. Once the
brochure has been set, it goes through quite a thorough
proofing<->correcting cycle. Nothing new here.
The tricky bit is that once the brochure has been signed off for
printing, the Quark doc holds the most up-to-date, accurate data. We'd
like to suck this data out and drop it back into the database
replacing the old content.
The simple question is: how do we maintain some idea of data structure
within Quark so that when we parse out the text collected from Quark
we know what we've got? This must be a question addressed a 100 times
before but I haven't found an answer despite quite some time spent
searching and browsing various sites.
Any ideas?
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.