Paul,
Sorry to disagree, but fixed pitch is _so_ much easier to lay out in an editor. Documentation flows nicely with variable pitch and fancy hidden formats, but for code (and Lily's input is a programming language) you just want the plain line-by-line ASCII. It is, as you say, industry standard; and that is for a good reason.
Regards, Martin On Tue, 2022-01-04 at 10:14 +0000, Paul McKay wrote: Hi Speaking as someone whose eyesight isn't quite as good as it used to be, I'd like to suggest that anything in a colour is also in bold so that there are enough pixels for me to see what the colour is.
And this seems the appropriate place to ask why the examples are all in fixed pitch Courier in any case. I know this is kind of industry standard but it's one I don't find particularly helpful. I was once adept on the card punch machines and mechanical typewriters, but I think most of us abandoned fixed pitch fonts long, long ago. I'd suggest a sans serif font so that there's a clear contrast with the Georgia used as the text font in the documentation. Helvetica, Franklin Gothic and Source Sans Pro look good but I realize they might not be available on some platforms.
HTH Paul McKay
On Mon, 3 Jan 2022 at 23:33, David Kastrup < dak@gnu.org> wrote: Flaming Hakama by Elaine <elaine@flaminghakama.com> writes:
> In this sense, it seems like the place that has the most potential use
> for helping people distinguish different data types is where the
> syntax is the most complicated and dense, which is in music entry.
>
> The ability to quickly distinguish articulations, dynamics, notes, and
> durations seems like it would probably be most useful to people
> reading examples in docs, since that is the most unusual aspect of
> lilypond syntax.
I find splitting a8 into different colors about as helpful for reading
music as coloring note stems differently would be for reading score
sheets: there is a standard place they are attached to anyway and there
is no particular reason to look elsewhere.
It would be much more useful to highlight note lengths separated by
space but still common to a preceding note or rest, like
\drummode { bd4 r r 4. 8 }
where the 4. is sucked into the second r likely unintentionally.
Highlighting this is helpful. When there is a general "angry fruit
salad" flavor pervading the highlighting with lots of colors everywhere,
there just is not a lot of attention one can draw to actually important
things.
|