Carl Peterson wrote
> Maybe not texidoc-wise, but it's something I thought about on its own
> merits. I'm personally not crazy about is as it would basically result in
> us creating a very specialized set of CSS parameters for a very specific
> thing that could be changed and completely removed or made incompatible
> with what is coded. That said, Paul is right. It is technically doable
> (and
> in a way that gracefully degrades to text browsers), but I'm not sure
> that's the ideal route from the maintenance side of things.
Those are good points. Using inline styles would be a way to address these
issues, while raising others... but maybe it wouldn't work with texidoc
anyway.
I gave a markup version a try:
\version "2.18.0"
\markup \center-column {
\box \pad-markup #1 {
\line \rounded-box \pad-markup #1
{ "Plain Editor" "Dedicated Editor" "IDE" }
}
\combine
\draw-line #'(0 . 4)
\arrow-head #Y #DOWN ##f
\box \pad-markup #1 \with-color #blue
{ "LilyPond input file(s)"}
\combine
\draw-line #'(0 . 4)
\arrow-head #Y #DOWN ##f
\rounded-box \pad-markup #1
{"LilyPond"}
\combine
\draw-line #'(0 . 4)
\arrow-head #Y #DOWN ##f
\box \pad-markup #1 {
\line \box \pad-markup #1 \with-color #blue
{ "PDF" "SVG" "PNG" "MIDI" "More..." }
}
}
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Pre-review-questions-about-image-s-and-translations-tp157874p157949.html
Sent from the Dev mailing list archive at Nabble.com.
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
