2014-07-17 17:10 GMT+02:00 Urs Liska <u...@openlilylib.org>: > For lilypond-devel: We had talked about this option for the LilyPond > manuals. Having had my first experience I think we should give that another > thought. Have a look at the commit > https://github.com/openlilylib/openlilylib/commit/ > 568c3ef1c70dfa5619ae3a5c20ff78e1cc5a6eb2 > to see how "much" code was necessary to achieve that. > > I don't know the documentation build process, so I don't know where one > could put that step in. What's necessary is to run python code to convert > simple <pre></pre> content to styled HTML (as in the referenced commit). >
No idea either. I just see that in the documentation it's used <pre> with classes "example" or "verbatim". > Additionally it's necessary to have Frescobaldi's python-ly installed on > the machine, so that would be an additional (weak) requirement for the > build system's configuration. (A developer would _not_ be forced to install > it, but without he would simply get plaintext output). > And it's necessary to add a CSS file to the distribution. > Added your comment to the tracker: https://code.google.com/p/lilypond/issues/detail?id=1005#c9 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
