I agree that this would be a huge task to take on and not being a coder, I can offer little help in that regard. That being said, I am certain that there are many on this list that live and die by imposition (myself included). I'm certain that you could get a number of insights as to what users would be looking for in an imposition package and also our views on what the strong/weak point of the various commercial packages are.
Working with the developers of one of those packages, I know that the job could probably not be done entirely within the scripting engine, there are just too many variables. While there are some very good commercial packages that work on a plug-in basis to QXP (in-position, etc.) their feature set is somewhat limited. A PDF based imposition solution would be an ideal companion package to Scribus. All that would be needed at this point would be to start talking feature set requests, i.e. PDF flat out, Job Ticket out, JDF out, etc. Mit freundlichen Gr??en/Best regards, Arron Robinson ---------------------------------------------------------- -----Original Message----- Message: 8 Date: Wed, 31 Mar 2004 10:47:30 +0200 From: "el Sism?grafo , S.L." <[email protected]> Subject: [Scribus] Imposition To: scribus at nashi.altmuehlnet.de Message-ID: <200403311047.30960.sismi at ctv.es> Content-Type: text/plain; charset="us-ascii" Though I made the initial proposal I totally agree with Louis and Craig. I think at the moment there are too many other things that need to be done. I also believe that there are two different things we are talking about: One thing is imposing other documents like tiffs through Scribus. This can be done quite well through scripting. What I was talking about is to impose entire documents layouted with Scribus before they are streamed to pdf or output device. This still is a _major_ issue because of the huge amount of factors like color sequence for the calibration bars, situation of the calibration bar, spacing between pages on the sheets, page orders, bleeds, etc. Although implementation can wait, I think the printer folks on the list should do the conceptual work for a plug-in. What should it do, how does it work (fully automated, template based, etc.). It would even be helpful to start with some code. Although the whole bloody thing will have to be rewritten at a later point (may be in a couple of years), this code would be helpful for the coder that wants to pick it up to see what the idea is. And also because I hate turning up with the odd "could you please..." without contributing anything. I also think that this should be started as a sort of sig (special interest group). Any proposals?
