-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Samstag, 20. September 2008 schrieb Karl Berry: > It is done in the lilypond manual. > > Gadzooks. Why on the earth do they do that?
It's done for the tables of different note names in various languages: http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Note-names-in-other-languages#Note-names-in-other-languages Since the note names are actually lilypond code, the whole table was wrapped in a @smallexample. Of course, feel free to suggest something better... > Within @example-like environments, we make spaces active in TeX, so they > get preserved in general. It seems to me that using @item or whatever > in such contexts is going to produce pretty suboptimal output, but if it > works for the Lilyponders, fine. Anyway, as far as the language goes, > we can say spaces are preserved in such places. Yes, makeinfo --html preserves the spaces and linebreaks, but since they are directly inside a <table>, browsers seem to simply ignore them (even though the table is inside a <pre>, which is not valid html, but oh well...) texi2html on the other hand tries to produce correct html and so wraps the <pre> inside every table cell, thus making the spaces and more importantly the line breaks appear verbatim: http://kainhofer.com/~lilypond/Documentation/user/lilypond/Writing-pitches.html#Note-names-in-other-languages Cheers, Reinhold - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI1XnOTqjEwhXvPN0RAkJKAKCn+TYfbWcldU3sRPiGF05YHEts9QCggCtd RqDX9k9Yr65LmpPPSRfHO2I= =xiKV -----END PGP SIGNATURE-----
