Hi all, Sorry if I don't get the gist of this conversation (I'm new, here, anyway), but isn't converting Chicken's manual to Texinfo format a bit waste of time? Because the way I see it, chicken.pdf isn't really counts as a *reference* manual: you know, the kind of document one would print and provide within hand's reach, or as an INFO file one would keep in an Emacs frame while coding Scheme in another. I use MIT Scheme's reference docs (and some of Chicken's own source codes) for that purpose, and it suits me fine (well, barely).
IMHO this is the right time to start redoing the docs, one that's sensible to be done in Texinfo, with separate tutorial, reference, usage manual and technical sections, one that's really decent to be called a reference document (the kind of docs Texinfo format is aiming at, I think). If anyone (with enough authority) willing to streamline the works, deciding what kind of contents would be included, I'm looking forward to contributing to a section or two. --- Mario Domenech Goulart <[EMAIL PROTECTED]> wrote: > ... > Because, as far as I know, we don't have a > wiki->texinfo > converter. > ... ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
