lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Let wordwrap-field and justify-field take non-strings?


From: Thomas Morley
Subject: Re: Let wordwrap-field and justify-field take non-strings?
Date: Sun, 2 Dec 2018 15:36:40 +0100

Am So., 2. Dez. 2018 um 15:09 Uhr schrieb David Kastrup <address@hidden>:
>
> Thomas Morley <address@hidden> writes:
>
> > Am So., 2. Dez. 2018 um 14:50 Uhr schrieb David Kastrup <address@hidden>:
> >>
> >> Thomas Morley <address@hidden> writes:
> >>
> >> > Hi,
> >> >
> >> > still musing about improving markup->string, I now stumbled across
> >> > \wordwrap/justify-field.
> >> >
> >> > Both have a condition to return visible output only if the catched
> >> > input is a string (using 'wordwrap/justify-string-markup' then),
> >> > whereas \fromproperty accepts markup as well.
> >> > Is this intended?
> >> >
> >> > One could go for markup? as well and use simple 'wordwrap/justify-markup
> >> > or
> >> > One could do the condition as (not (string-null? (markup->string ...))).
> >> > (Currently markup->string will not return anything else than an empty
> >> > string, as said I'm working on improvements)
> >> >
> >> > Opinions?
> >>
> >> A string is structured by spaces and newlines, a markup list has already
> >> separated elements.  How would you naturally deal with single markups?
> >
> > That should become the duty of markup->string
> > Like:
> > single-markup = \markup \line \italic { Lorem ipsum dolor sit amet }
> > #(write (markup->string single-markup))
> > =>
> > "Lorem ipsum dolor sit amet"
>
> But then any markup formatting of the fields would get lost without
> warning?

Well, indeed. This could be a feature or it could be undesired. Thus I
asked for opinions.
If we want to keep the formating we could probably do the same as in
fromproperty.

Cheers,
  Harm



reply via email to

[Prev in Thread] Current Thread [Next in Thread]