>>>> In message <Pine.LNX.4.10.10003232253120.7731-100000@...>
>>>> On the subject of "Re: cron job"
>>>> Sent on Thu Mar 23 16:59:19 EST 2000
>>>> Honorable Stefan <stefan@...> writes:
>> On 23 Mar 2000, Sam Steingold wrote:
>> > what about the automatic docbook/xml -> html publishing?
>> > I envision it like this: there should be a cvs checkin hook (or a
>> > nightly cron): whenever an XML file is checked in, it is published in
>> > HTML and the resulting html file is made available on
>> > http://clocc.sourceforge.net.
>> > all these auto-generated files should be searchable.
>> I back this up, principally. But I am still busy thinking how we can
>> acomplish this, in detail. The problem is the physical distinction
>> between the machine, which handles cvs-requests and the machine
>> which hosts the web-server. AFAIK, their are different.
can we check out the sources to the web machine?
an alternative is, of course, the same as your solution for the snapshot
problem - checkout to your machine, publish and upload.
>> > On a second thought, there might be some XML files which are not the
>> > principal docbook/xml files (like entity files, chapters &c), so
>> > only files name/name.xml should be exported.
>> Can you elaborate on this idea?
much like \include in TeX, docbook/xml allows one to have different
parts of the same book in different files, but these files cannot be
processed separately from the main file. let us decree that the main
file for the package PACKAGE will be PACKAGE.xml, and this will will be
published (i.e., you run jade on it and it will create a single file
PACKAGE.html which you then upload to sourceforge).
At least this is my understanding.
>> > I can add a directory clocc/doc and put a file with useful docbook/xml
>> > entities which I grew when translating clisp impnotes to docbook/xml.
>> > (so that you will write &car; instead of <ulink url="http://www.lisp.org/HyperSpec/Body/fun_caadrardar.html"><function>car</function></ulink>)
>> that sounds great! :-) Import it, please!
okay, I will.
Sam Steingold (http://www.podval.org/~sds)
Micros**t is not the answer. Micros**t is a question, and the answer is Linux,
(http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation.
The only intuitive interface is the nipple. The rest has to be learned.