http://codereview.appspot.com/4172047/diff/1/scm/define-markup-commands.scm File scm/define-markup-commands.scm (right):
http://codereview.appspot.com/4172047/diff/1/scm/define-markup-commands.scm#newcode1033 scm/define-markup-commands.scm:1033: #:with-dimensions (cons 0 middle-width) '(0 . 0) #:postscript (string-append "0.25 setlinewidth 1 setlinecap [0 1.5] 0 setdash " (number->string offset) " 0.12 moveto " (number->string middle-width) " 0 rlineto stroke") On 2011/02/15 00:56:02, Carl wrote:
I don't think we should accept postscript markups as part of the
distribution.
They will break the SVG backend.
We should ask for all markup functions that become part of the
distribution to
be supported in all backends, IMO.
I agree. Except for `setdash', the rest of the \postscript string argument can be written with \path (and its arguments) instead. This command supports both primary backends. http://codereview.appspot.com/4172047/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
