Re: [GT] Writing indicators cookbook

["Robert A. Schmied" <ras AT acm.org>]

R P Herrold wrote:
> On Sun, 9 Mar 2008, Weigert, Thomas wrote:
>
> > I think it is useful to archive the PDF file, as not every user will
> > have the latex tool chain installed (I dare say that more users might
> > have MS word than latex). Providing the PDF is a matter of convenience.

aloha r

thomas has hit that nail on the head, convenience for the user. i'm toying
with a web site alteration to link the pdf so it can 'read' via browser.

most, if not all, of the incantations to turn tex into something a bit
more user friendly have been wrapped in a makefile of some form. it is
possible that the gt server has all the necessary bits and pieces to
daily update the pdf from the tex. thomas, could you supply the
'latex tool chain incantations' and other info needed to re-create the .pdf
from the .tex so i can query the admin on the availability of support.

> Don't go woozie on me here ... As TeX is freely available for 'nix, 
> Apple, and Windows operating environments, and the proprietary product 
> on only the last two and only for purchase, a universe composed of Adam 
> Smith'ian rational actors (we are after all about EMH and investment and 
> trading here ...) should clear with more abundance in the TeX corner. ;)

freely available provided one has 100mb plus of space available.
yea, even in the days of 500gb disks some of us are still using pre-historic
9gb drives ;-)

> ...lending a courtesy build is a different analytic case, but in terms 
> of economic rationalism, better and free beats less featured and priced.
>
> drilling in up-to-date perldoc throughout also comes to mind

if a module with new pod is committed the pod will be available via
the web site within 24 hours.

> Who do I speak to about getting CVS commits?

actually, not that it truly matters, it's subversion now ;-)

query the admin, and gt owner Raphaël Hertzog < raphael at ouaza dot com >

the devel list is intended to serve as the initial collaborative development
vehicle. contributors are encouraged to post patches, whole modules
(or even tarballs) to the list for collaborative review, comment and finally
a commit.

i'm trying to stay abreast of the changes, and am doing my best to keep
commit churn to a minimum, only to avoid new users getting broken code.
i have 10 (9 as byname just changed again) revisions about to be committed,
but i want to run a few more tests just to be sure...


aloha

ras


> - R