On Sun, Sep 26, 2010 at 7:47 PM, Mark Polesky <markpole...@yahoo.com> wrote:
> David Kastrup wrote:
>> The code is likely a one-liner if done correctly, but I
>> already spent 10 minutes digging through the details.
>>
>> So I'll turn to wait mode right now.
ok.
> This work may have already been done by the texinfo
> developers; I told them about it some months ago. IIRC, the @w
> trick works for info and pdf, and the html version is fixed
> in the texinfo sources, but I don't think they've released a
> stable version that includes that change, and I didn't have
> time to go learn CVS.
Yes, but I'd rather not have @w{} everywhere in our code, partly due
to the "semantic vs. ouput commands" thing, but mostly due to the
annoyance+maintenance issue. I'm interested in a general "treat all
@code{} as if it were wrapped in a @w{}" solution.
It seems like we're still waiting for a stable release of texinfo (not
that we can really complain about time between stable releases) before
being able to really clean up a lot of our doc generation stuff.
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
