Graham Percival <gra...@percival-music.ca> writes:
> On Sun, Sep 26, 2010 at 08:31:10AM +0200, David Kastrup wrote:
>> Mark Polesky <markpole...@yahoo.com> writes:
>>
>> > +Use the @code{@@c...@{@dot...@}} command when referring to
>> > +individual language-specific tokens (keywords, commands,
>> > +engravers, scheme symbols, etc.) in the text. Ideally, a single
>> > +...@code{@@c...@{@dot...@}} 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.
>
> Nope; we get line breaks in stuff like @code{\override
> Voice.textscript #'padding = #3}. :(
>
> I'm not certain whether this constitutes a bug with texinfo itself
> (i.e. I'm not going to argue about what the default formatting should
> be), but it would definitely be nice if we could make our backends
> (texi2pdf, texi2html) avoid newlines in such material. I can't
> remember if this made its way onto the tracker or not.
I seem to remember that in TeX hyphenation is more or less a font
property. If that is not the case, one can likely do something like
@iftex
@co...@hyphenchar@t...@font=-1 }
@end iftex
in order to turn off hyphenation for the font selected for @code
passages, obviously for those backends implemented with TeX.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
