Jean-Marc Lasgouttes wrote: > Alfredo Braunstein wrote: >> Angus wrote: >>>In order to achieve that we need a new member function to perform >>>any necessary manipulation of the external material. To my mind, it >>>makes sense here to write these instructions to an ostream also. We >>>end up with two separate ostreams, one containing instructions on >>>how to manipulate external files and one containing the >>>latex/docbook document. > > Note that this means that all this file manipulation will reside in > sh scripts, which will really be unix-specific, and this is not a > good design IMO. Of course, we could use lua :)
The code to generate the script would reside in graphics/GraphicsConverter.C (probably renamed or even split up). That's pretty encapsulated, don't you think? Also, I see Ruurd's native Windows port using this shell script stuff without problems. Isn't that the mingw project? http://www.mingw.org/ -- Angus
