Jon wrote: >> Is it >> so much bother to open Scribus to print a file? >> > > Yes, because that requires a human being. > > I need to be able to print (or export to PDF or ghostscript) SLAs with > no human intervention. After creating letter or form templates and > having our database merge arbitrary account information selected at > arbitrary times by any of our users for an arbitrary number of > templates, I need to be able to print them with no human intervention. > We are already doing this with a deprecated proprietary word processor > (wordperfect 10) which is the last mission critical application forcing > us to depend on a proprietary deprecated "operating system". > > Even if Scribus could automatically open and run Scribus Python scripts > from a shell (scribus --run-script <script.py), while ugly as pages > would get printed client-side as opposed to server-side, that would > immediately make Scribus exponentially more valuable as it's the perfect > authoring tool for letters and forms. > This sounds like a job for one or more scripts, but right now beyond anything Scribus can do. There was this script
http://wiki.scribus.net/index.php/Importing_addresses_from_a_text_file which I wrote to show one way to import information from a text file for incorporation into a document. We just don't have a command line facility of using Scribus as of yet. Greg
