On Sun, Oct 22, 2006 at 09:01:28PM -0600, Richard Lyman wrote: > > As for what it sounds like you want to do... I'm guessing that the PDF > will be the product and HTML / Word / whatever is only the means to > manage the data between people before producing the PDF - right? In > that case...
Yep. However, the HTML / Word / whatever, is also the file to leave behind when I eventually get released from a Church calling. > You could use a scripting language to output PDF's and provide an > interface to manage the data. A quick google for 'ruby pdf' has a nice > intro in the second link ( > http://www.artima.com/rubycs/articles/pdf_writer.html ) to > PDF::Writer. As much as I dislike Rails (for taking over the mailing > lists), you could whip up a system in Rails that presented a web > front-end to manage the data and that output PDF's either by producing > LaTeX files or through something like PDF::Writer. Up to now, this is what I've been doing. I've got a web frontend in Django, and I've been doing all of the editing there. The PDF is generated from within Django using a LaTeX template I made. This works great for current maintenance, but I can't leave it behind when I eventually leave, because I can't assume that other people can maintain my code or even program at all. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
pgpqffAtAnQW5.pgp
Description: PGP signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
