On 2010/10/26 08:21:41, Mark Polesky wrote:
Well... Okay, yeah, but see this:
http://kainhofer.com/%7Elilypond/Documentation/contributor/syntax-survey.html#miscellany
I'm the one that wrote the @var description there. And yes,
the rationale is simplistic: "This improves readability in
the PDF and HTML output." But I think Neil's impulse to
format it that way matches the spirit of the rationale, no?
And I certainly wouldn't be opposed to instituting the same
policy for A.17, though of course that would be best left
for a different patch than this one.
I think that wrapping a variable declaration in a code declaration is
undesirable. It complicates the format of the documentation, for very
little benefit (if any).
If we want to change the format of @var{} in HTML and PDF format, we
ought to be able to do that in our texinfo program.
Or alternatively, we should get a different texinfo macro, e.g. @var{}
for outside of code, and @codevar{} for use inside of code.
THanks,
Carl
http://codereview.appspot.com/2275042/
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
