>> LSR files sometimes refer to the manual. Example:
>
> I almost consider this a bug, especially if they reference the LM.
Yep.
> ... we *could* add a special "html" command for these in LSR. They
> would do nothing in the main LSR view, but when we run makelsr.py,
> we could change the new "html" command into @ref{}. Depending on
> how the build process works, these might be able to link back to the
> proper location.
>
> However, I really cannot see this being worth the (relatively
> speaking) enormous effort to modify LSR, modify makelsr.py, possibly
> modify the build process, and test the entire thing. I think we're
> looking at 20 hours of work to support something that perhaps a
> dozen badly-worded snippets use.
OK.
> To anticipate a possible objection: the snippets are not designed to
> teach lilypond basics.
Exactly.
A logical corrolary: LSR files must not refer to the documentation (or
rather, to exact locations in the docs); instead, the docs should
refer to LSR files. All references should be thus removed.
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
