Text formatting inside `\wordwrap-field`

How do I apply formatting to text in a header field which is destined to be inside a `\wordwarp-field` command. Say, for instance, that I wanted to italicize the words "incididunt ut labore" in the following snippet (taken from the documentation for `\wordwrap-field`): %%% BEGIN snippet %%%

lyluatex inline question

Hi all, So far lyluatex is working brilliantly for me. A question about setting a musical example inline. To make the staff smaller to match the surrounding text I need the inline-staffsize command but I can't get this example to work. \lilypond[insert=bare-inline, inline-staffsize=8]{a4 a8 a}

Re: bookparts (OT)

On 12/03/18 21:47, Noeck wrote: > Hi all, > > thanks a lot to all how replied to my questions! > I got quite discouraged by the first reply but having my questions > (mostly) confirmed helps a lot. > > Summary of the main points: > > - \bookpart is something like a scope for \paper settings > -

Re: Right aligned text in header

On 3/13/18 5:02 PM, Thomas Morley wrote: Hi, do you mean like below? Based on http://lsr.di.unimi.it/LSR/Item?u=1=765 #(define (general-column align-dir baseline mols) (let* ((aligned-mols (map (lambda (x) (ly:stencil-aligned-to x X align-dir)) mols))) (stack-lines -1 0.0

Re: Right aligned text in header

2018-03-13 20:31 GMT+01:00 Br. Samuel Springuel : > I'm creating a custom bookTitleMarkup for a project I'm working on and have > some lines which are setup like `meter` and `arranger` in the default > template (two blocks of text, one flushed left the other right, on the

Re: Thriple flat/sharp glyphs...

Hi Torsten, I am in favour of version 3 (or between 3 and 4). Equally spaced, full-sized flats with maximal overlap. I think, saving horizontal width is important. I like your "intermediate 3/4 pdf". In a very large size (your pdf 400%) they look perfect to me. It is hard to tell with the

Right aligned text in header

I'm creating a custom bookTitleMarkup for a project I'm working on and have some lines which are setup like `meter` and `arranger` in the default template (two blocks of text, one flushed left the other right, on the same line). However, on one of those lines the header properties to be used

Re: can the leading \markup command be eliminated in a new markup command?

Hi David, > You either define an event function or a markup command. […] > One is the markup, the other is a text script post event. Markups can > be used in a variety of circumstances (as text scripts, as lyrics, as > part of other markup, as tempo strings, as mark texts and so on). Text >

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi David, > >>> Is there any technical reason not to make *every* markup function work >>> like this? >> >> There are markup commands and event functions and they are in different >> name spaces. > > Sorry for pushing for more

Re:Thriple flat/sharp glyphs...

> From: Werner LEMBERG > Subject: Re: Thriple flat/sharp glyphs... > > Nice work! > > > 2. Abraham's equally compressed flats > > > > Both flats are equally compressed as a compromise, thus keeping the > > original glyph width: > > > >

Re: Thriple flat/sharp glyphs...

Hi Torsten, I'm undecided between the second and the third. Would it be possible to compare them in a musical example? 2018-03-13 12:38 GMT-03:00 Werner LEMBERG : > > Nice work! > > > 2. Abraham's equally compressed flats > > > > Both flats are equally compressed as a compromise,

Re: Thriple flat/sharp glyphs...

Urs Liska-3 wrote > If I had to choose between 3) and 4) I would go for 4), but actually I'd > suggest to go for something between those two. Good point. To narrow down the number of suggestions, I just took the extreme cases. If we go for natural width flats, the overlap can be optimized. Urs

Re: Edition Engraver bug?

Hi Jan-Peter, Thank you for your work! I will test the changes later today and let you know how it results. 2018-03-13 7:47 GMT-03:00 Jan-Peter Voigt : > Am 13.03.2018 um 11:37 schrieb David Kastrup: > >> Jan-Peter Voigt writes: >> >> Hi Stefano, >>> >>> I

Re: can the leading \markup command be eliminated in a new markup command?

Hi David, >> Is there any technical reason not to make *every* markup function work >> like this? > > There are markup commands and event functions and they are in different > name spaces. Sorry for pushing for more clarity/understanding, but: is it [in terms of behaviour] that the

calling lilybin (or similar) as a service triggered from a [JavaScript?] form in a web page

Hello all, Has anyone tried to set up a form (e.g., Javascript) in a web page which, when submitted, triggers a Lilypond-on-server (LoS?) application/environment (e.g., lilybin.com) and returns a PDF? I'd like to offer some music and music education documents and templates on my website, but

Re: Thriple flat/sharp glyphs...

Nice work! > 2. Abraham's equally compressed flats > > Both flats are equally compressed as a compromise, thus keeping the > original glyph width: > > > This is my favourite. Werner

Re: Thriple flat/sharp glyphs...

Hi Torsten, thank you for that comparison. Am 13.03.2018 um 15:52 schrieb Torsten Hämmerle: ... Double-flat alternatives in comparison In the old discussions mentioned in some of the answers, Abraham proposed a compromise that kept the original glyph width by applying an average compression

Re: Thriple flat/sharp glyphs...

First of all, Thank you very much for all the feedback! Sorry I didn't dig the archives myself, but initially I took the original Feta designs for granted and carved in stone. Where did the original double-flat design come from? Music(X)TeX was a good guess, but the Music(X)TeX accidentals look

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi David, > >> %%% SNIPPET BEGINS >> \version "2.19.80" >> >> cue = >> #(define-event-function (text) (markup?) >> #{ ^\markup \bold #text #}) >> >> { c''\cue "This is the cue." } >> %%% SNIPPET ENDS >> >> If you don't want to bake

Re: can the leading \markup command be eliminated in a new markup command?

Hi David, > %%% SNIPPET BEGINS > \version "2.19.80" > > cue = > #(define-event-function (text) (markup?) > #{ ^\markup \bold #text #}) > > { c''\cue "This is the cue." } > %%% SNIPPET ENDS > > If you don't want to bake the direction in, use - instead of ^ . Thanks for that! Is there any

Re: Edition Engraver bug?

Am 13.03.2018 um 11:37 schrieb David Kastrup: Jan-Peter Voigt writes: Hi Stefano, I have been looking into the issue and created a branch 'refactor-override' for the edition-engraver. The following is changed in there: * Overrides are not applied "by hand" but send as a

Re: Edition Engraver bug?

Jan-Peter Voigt writes: > Hi Stefano, > > I have been looking into the issue and created a branch > 'refactor-override' for the edition-engraver. > The following is changed in there: > * Overrides are not applied "by hand" but send as a StreamEvent so > that once is handled by

Re: Edition Engraver bug?

Hi Stefano, I have been looking into the issue and created a branch 'refactor-override' for the edition-engraver. The following is changed in there: * Overrides are not applied "by hand" but send as a StreamEvent so that once is handled by lily and not the EE * Override (and Revert, Set,

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi all, > > Sorry if this is a silly question… but can this function be modified such > that the user can use > > { c''^\cue #"This is the cue." } > > instead of > > { c''^\markup \cue #"This is the cue." } > %%% SNIPPET BEGINS

Accessing grobs generated by a music event?

Hello everyone, I was wondering, is there a way to, given a 'NoteEvent (or 'EventChord, or whatever other music expression for that matter) find the grob or grobs that it generates? Although I don't know how Lilypond actually processes input, I suspect that this isn't possible. I imagine that if