The plone workflow systems are absolutely over-customizable, if you need to figure out a very specialized way to approve changes, plone can do it.<br><br><div class="gmail_quote">On Fri, Feb 13, 2009 at 1:50 PM, John Reese <span dir="ltr"><<a href="mailto:jwreese0@comcast.net">jwreese0@comcast.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
FWIW, Plone has excellent version control systems (many, in fact),<br>
excellent templating capabilities, and there are plenty of document<br>
conversion modules. Specifically I remember seeing one or more PDF<br>
generators.I think I have seen LaTEX and DocBook support, but it has<br>
been awhile. There is a lot of XML support in the Plone community so you<br>
could use that data format to shuttle between various markup languages.<br>
<font color="#888888"><br>
JR<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Scott Dier <<a href="mailto:scott@dier.name">scott@dier.name</a>><br>