Il giorno mar 15 mar 2016 alle 4:12, Mark D. Blackwell <[email protected]> ha scritto:
 I prefer the center-align.
I think that, as long as each definition begins with a capital (it should be
 "A Scheme type predicate...") and there's some padding between each
 definition, it should be readable.

 See attached example. What do you think?

I'm puzzled by your attached example. It doesn't seem to be an example
of center-alignment with padding beginning with a capital. Instead,
the word "Two" lines up vertically with the start of the second set of
"Lorem ipsum" text. This alignment is exactly what I originally meant
would be better. :)

You are probably seeing that example at full width.. Try to resize the browser window to half screen and you'll see that in my first example, as in the attached screenshot, the "Two" is not lined up vertically to the second set of lorem ipsum; it is centered.

Find attached a second example where there's a real top alignment, as defined by this CSS rule:

table td {
 vertical-align: top;
}


As to your words about your preference, I agree that adding some
padding between each definition would mostly solve the readability
problem. Yet (still) I feel it's less aesthetically pleasing than
top-alignment. And from readers, it calls for more visual "seek"
effort. BTW, on that page of the PDF version of the manual, I observe
the "cells" already are top-aligned (or the equivalent).

This is true. There's also more padding than in HTML.
I agree that it's more readable.

Lastly I
should mention that in general such padding would (at least slightly)
increase the size of an HTML manual, thus making any given browser
window hold slightly less information.

If a small padding improves the readability, this is good and I don't mind about the HTML manuals being slightly longer. Who cares for this?

Anyway, I can try and make a patch as soon as I have some time (very few spare time recently).


   One   Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
         eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
         minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip
         ex ea commodo consequat. Duis aute irure dolor in reprehenderit in
         voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur
         sint occaecat cupidatat non proident, sunt in culpa qui officia
         deserunt mollit anim id est laborum.
   Two   Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
         eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
         minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip
         ex ea commodo consequat. Duis aute irure dolor in reprehenderit in
         voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur
         sint occaecat cupidatat non proident, sunt in culpa qui officia
         deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet,
         consectetur adipisicing elit, sed do eiusmod tempor incididunt ut
         labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud
         exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
         Duis aute irure dolor in reprehenderit in voluptate velit esse cillum
         dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
         proident, sunt in culpa qui officia deserunt mollit anim id est
         laborum.
   Three Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
         eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
         minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip
         ex ea commodo consequat. Duis aute irure dolor in reprehenderit in
         voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur
         sint occaecat cupidatat non proident, sunt in culpa qui officia
         deserunt mollit anim id est laborum.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to