> (or rather, the empty markup)... What do you mean? I don't see an empty markup.
> So it must be the current composer... Is it too long? IC, Josh On Fri, Sep 26, 2014 at 3:44 PM, Abraham Lee <[email protected]> wrote: > On Fri, Sep 26, 2014 at 1:50 PM, Joshua Nichols <[email protected]> > wrote: > > Thanks Abraham. See attached. > > Thank you for the tremendous and hard work you have put to explore > alternate fonts. I am in debt to you (for which I might just donate ;) ). > > IC, > > Josh > > On Fri, Sep 26, 2014 at 2:47 PM, Abraham Lee <[email protected]> > wrote: > >> On Fri, Sep 26, 2014 at 1:23 PM, Joshua Nichols <[email protected]> >> wrote: >> >> I wonder if this problem has occurred with 2.18.2, but I have not tried >> it. >> >> Anyone understand why the composer is coming out all the way to the right >> of the margin? see attached. >> >> Sincerely, >> >> Josh >> >> >> Josh, >> >> I, personally, haven't noticed anything like that as a result of using >> the new music fonts, but that doesn't mean you aren't. Could you please >> post us your exact code (maybe attach the .ly file) that results in this >> error? I believe that there has been some discussion in another thread >> about this composer mis-alignment error already, but let's see if that is >> indeed the issue or if it's something else. >> >> Regards, >> Abraham >> > > Josh, > > I compiled your file on 2.18.2 and it worked just fine with the composer > in the right place, so it must be the current composer (or rather, the > empty markup) spacing issue. > > Regards, > Abraham >
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
