Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
References: <m1iot55mmi.fsf@SEAM.local.i-did-not-set--mail-host-address--so-tickle-me>
Content-Transfer-Encoding: 8bit
Message-ID:  <6F382265-CAB2-44AC-8B21-6EEEAE3BE8AA@frycomm.com>
Date:         Tue, 28 Jan 2014 15:03:10 -0500
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: William Adams <will.adams@FRYCOMM.COM>
Subject: Re: Feasibility of GUIs for authors and class designers in LaTeX3
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <m1iot55mmi.fsf@SEAM.local.i-did-not-set--mail-host-address--so-tickle-me>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

The big issue is exposing the features / options in a consistent way which an automated system can access.

I just worked up as a proof-of-concept here at work an AppleScript which takes an InDesign document and:

 - extracts the page size
 - extracts the filename/path of a graphic on a layer named Graphic
 - extracts the font, size, color, position and rotation information from the boxes on a ``Text'' layer (had justification, but ran out of macro arguments and couldn't use it)

and writes all that out into a .txt file which xelatex is then able to read in and will use to determine the formatting used when typesetting a .cvs

William

-- 
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.