(sorry, I forgot to send a copy to the mailing list)
Jason McLaughlin wrote:
> Lookin' good, what do you use to create docbook's? I tried getting the openoffice import/export filters to work, with no success.
I have modified it manually, it was a bit long but that works now.
Update now and look at doc/Makefile. This Makefile is stupid because
every one who download it must change the path for the stylesheet.
Anyhow, I think taht only developers will compile the manual and that
commintting the steelsheet in the repository is not a good idea...
The manual is *far* from beeing complete. I'm still working on it,
especially on the way of how we can integrate it in the web interface.
Docbook don't seem to be cooperative to provide us with string based
links. For example, to find the cache section, an easy way is to request
cache.htm or manual.htm#cache, but jade makes files like this : c272.htm...
> How do you feel about protocol.c being broken into seperate files: proto_http.c, proto_ftp.c, and proto_connect.c (leaving protocol_start in protocol.c) ?
> protocol.c is becoming a little unmanagable.
> We could also move a huge chunk of the code in main.c ( between the protocol_start: and skip: labels) into protocol_start itself.
Totally agree with you. This is an additional step toward modularity.