Firstly, this is great.  Thanks.

Actually, there is no need to put it on cron.  The userguide only changes when a new version of CI is released, so based on our current release cycles, that would only be one every 8 to 10 weeks.  So if you wanted to just manually run it when a new version is released, that would save some cycles and bauds.

This is great. Thanks, alienne!

Derek,

Okay, can do! Do you want me to make a list of where the documentation URLs are inconsistent or otherwise making my head hurt, and they can be looked at for the next version?

Adrienne

Also, if i get really ambitious I’ll try to do some kind of on-the-fly PDF transformation. I keep meaning to learn more about some of the common tools available to do that in. (fPDF, etc.) The problem is that (as i keep telling colleagues and friends), i am not a developer—i just play one on TV. *wry grin* So these things do take me awhile to pull off.

alienne.  Sure, sounds great.  What would be ideal for me is to get 1 big list from you rather then 100 small emails.  Could you get them all into 1 message and send to me? 

Its a little known secret, but I’m taking a vacation shortly, so this probably won’t get addressed for 2 weeks or so…

Sure, Derek. I’d definitely have done them in one big list anyway. There’s a couple of places where anchors are unique in a document but not globally unique, which confuses things and i’m having to replace them manually—but most of the problems are that inter-document links sometimes look like this: “./something/something.html”, sometimes look like this: “/something/something.html”, and sometimes like this: “something.html”. Without, so far as i can tell, any actual rhyme or reason.

Being an EE person, i’ve long since fallen into the habit of doing EVERYTHING as root-relative (makes it easier to declare images in pages which may get called from a number of different fake subdirectories), which might be the best strategy to use here too.

Adrienne