[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: Doc fixes for \applyOutput ... ok to push?
From:       David Kastrup <dak () gnu ! org>
Date:       2010-09-26 6:31:10
Message-ID: 87lj6puic1.fsf () lola ! goethe ! zz
[Download RAW message or body]

Mark Polesky <markpolesky@yahoo.com> writes:

> Okay, then how's this?

Looks good.  There are a few things I am not sure about:

> +Use the @code{@@code@{@dots{}@}} command when referring to
> +individual language-specific tokens (keywords, commands,
> +engravers, scheme symbols, etc.) in the text.  Ideally, a single
> +@code{@@code@{@dots{}@}} block should fit within one line in the
> +PDF output.

I have not followed Texinfo development closely, but I think that most
of the time, there were no line breaks in typewriter fonts done at all.
If that is indeed the case, the last sentence should rather be

Since @code{@@code@{@dots{}@}} and @code{@@samp@{@dots{}@}} commands are
placed as a part of the surrounding paragraph, they should only contain
code passages, never exceeding one line in the PDF output.

-- 
David Kastrup


[prev in list] [next in list] [prev in thread] [next in thread]