Yeah, my university formatting requirements are crazy also. This allowed me to have one source that outputs (nicely) to a bunch of different formats, including the university PDF requirement.

This uses an existing format, restructuredtext, not a new markup format.

Pull requests accepted :)

It's using http://code.google.com/p/latex-makefile/ which is a really awesome makefile. It has nice colored output and throws away all the garbage output.

At least you can build your own scripts around this stuff. Building LaTeX for me goes like this:

I use vim, change a line, and hit ":w". My git-onNotify [0] script detects a change and issues "make show". The Makefile uses rubber or latexmk to build a pdf, then issues "gnome-open $PDF", which opens the new version in my pdf viewer. If my screen is tiled, the preview on the side just updates.

Essentially, I just save my tex file and wait for the change.

[0] https://github.com/beza1e1/dot/blob/master/bin/git-onNotify

it had to be done

intentional :)

Love the name, laughed my ass off ;)

Disclaimer: I'm immature...

Oh.. OOOHH. I get it :)))))

Other output formats: http://jterrace.github.com/sphinxtr/

GitHub repository: https://github.com/jterrace/sphinxtr

Yeah, I'm in no way proud of that beast of a code. There are a couple things at play here:

1. The js.js API is currently very low-level, which makes it verbose and difficult to use. There's a lot of room for improvement.

2. The twitter script was actually chosen because it's complex. It has a ton of boilerplate code that you'd probably be surprised is in there.

3. A lot of the code written could be generalized into a generic virtual DOM interface library that is not specific to this twitter script. Things like screen.width and screen.height are common properties that would be accessed by many different scripts and so could be generalized.

Something like this would be awesome:

  var env = {local1: function (){}, local2: "blah"};
  js = new JSJS(env);
  js.eval("console.log('I am evil!'); local1();");

The sandboxing of third-party scripts that we talk about in the paper (http://www.cs.princeton.edu/~jterrace/docs/jsjs.pdf) is one possible use case

This is because I'm converting to an i32 rather than a double. It should be able to be fixed relatively easily.