On 9.06.05, Angus Leeming wrote: > Jean-Marc Lasgouttes wrote: > > 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 :)
> > 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. Unfortunately, This script both stores and manipulates the raw data ... while I would prefere a clear distinction of raw data, templates and code, especially, if we want the developers of the lfuns to provide/update the (basic) documentation. G�nter -- G.Milde web.de
