Jean-Marc Lasgouttes wrote: > chr> Going off on a slight tangent, what if we put some cursory > chr> documentation of the lfuns in the *source* code using wiki > chr> markup? Then I could write a simple script that periodically > chr> extracts that markup and inserts it into some suitable wiki > chr> pages? > > chr> It's a bit off a hack, but might be useful in this particular > chr> instance. Especially since we'd avoid maintaining separate > chr> documentation of the lfuns, and anything that makes it easier for > chr> the developers to document changes to the lfun ought to be a good > chr> thing... > > I'd propose to use the exact inverse method: maintain the lfun > documentation outside of source tree in an easy to parse format, so > that we can decide to merge it in the sources later :) > > This lfun documentation is not going to appear in LyX 1.4.0 anyway, > and I do not know when someone is going to do it in 1.5.0cvs. > Actually, I predict that if this point is raised on the list, it will > transform itself into a thread on the proper choice of a scripting > language and then die... > > I guess this can be done from outside as a documentation project. If > the file format is straightforward enough, it could even be made > available from inside LyX.
Have a look at lib/generate_contributions.py which is used to generate lib/CREDITS, credits.php and blanket_permission.php . I guess that the idea of "one source, several outputs" is what you're looking for here too. -- Angus
