Dear Lilyputians,

I've almost got it (see attached)
Well, I've got into two commands, so that I can do
***
\markup{ \who{someone} \says #"What he says" } 
***
I'd like to take it one step further to and combine them both into one
command with two args: (markup? string?). It's a small thing, but it would
let me take out the third command and (I think) the outer curly-brackets.
According to the 2.9 docs (chapter 12) this should be possible, but the
example of define-markup-command in said chapter has only one argument. Can
someone show me an example of a define-markup-command with two, a (markup?)
and a (string?).

Fr. P





\version "2.8.3"
% The command "who"
#(define-markup-command (who layout props args) (markup?)
(interpret-markup layout 
	(cons (list '(font-size . 2) )  props) 
	( markup #:hspace 12 #:with-color (x11-color 'firebrick) #:italic args #:hspace 5 ) 
	)
) 
% The markup command "says"
#(define-markup-command (says layout props arg) (string?)
	(interpret-markup layout 
	(cons (list '(font-size . 2) ) props)
	(markup #:override '(line-width . 60) #:fill-line ( #:justify-string arg))
	)
)
% The file that uses them:
\book{ \markup{ \who{Garaganidse:} 
\says #"After Christianity had been declared the state religion in 326, Christian music became established in Georgia - on the one hand from Syria and Palestine and on the other from Byzantium.  Of course, the influence of the religious music of these lands was in this period entirely unavoidable. Original Georgian works were created as early as the fifth century, but from the seventh century, Georgian church songs began to be free from outside influence.  During this time, when the influence of folk music was becoming  great, polyphony gained entrance in large and increasing measure.  The Georgian text and the principles of Georgian polyphony became the basis of a total nationalization of church songs." }
	 } 
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to