I'm probably the ideal person, but I'm away at a music camp for the next week, so will have very little time. If this request could wait until the 26th, I'd have much more time.
The short answer is that we use texinfo, which has a few nice parts but a few bad parts. I think it's the best documentation format for nicely-formatted pdfs and html output (at leats, that seemed to be the case in 2008), but there *are* some really annoying parts. If you start looking at texinfo and try to think of specific questions about how it might work with your project, I could give more specific answers. :) Cheers, - Graham Percival On Fri, Jul 16, 2010 at 12:13:02PM -0400, Arle Lommel wrote: > Apologies for a question not directly related to Lilypond, but is there > anyone who works with the documentation for Lilypond on this list with whom I > could interact privately? I am working on a totally unrelated open-source > project and we we are faced with about 500 pages of legacy documentation in > Word that we need to port to the web in a more friendly format than Word. > Lilypond’s documentation seems like an ideal model for me, and I’d like to > get a better picture of what might be involved in order to arrive at that end. > > Best, > > Arle > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
