Re: Interactive PDF Link to Notes in Preview

Il giorno lun 9 lug 2018 alle 7:26, Mats Behre <"mb.maillists"@gmail.com> ha scritto: On 2018-07-08 19:56, Federico Bruni wrote: I found this: https://superuser.com/questions/548119/how-do-i-configure-custom-url-handlers-on-os-x and downloaded SwiftDefaultApps. It works on High Sierra

Re: Fingering position in polyphony face to sharp glyph. Bug?

Simon Albrecht-2 wrote > I went to the issue tracker so this doesn’t get lost – it seems to be > related to or a subset of > ;. Hi Simon, While the descriptive title "Fingering collision with accidentals" of issue 3692 more or less describe

Re: Fingering position in polyphony face to sharp glyph. Bug?

2018-08-02 12:10 GMT+02:00 Torsten Hämmerle : > Simon Albrecht-2 wrote >> I went to the issue tracker so this doesn’t get lost – it seems to be >> related to or a subset of >> ;. > > Hi Simon, > > While the descriptive title "Fingering collisio

Re: layout of markup text (Peter Gentry)

On 02.08.2018 10:43, Peter wrote: Thanks Simon yes sometimes I am not sure what environment the interpreter is in, especially when it is expecting a music Element or not. It's obvious in the simple case but can be confusing in a more (unessessaryily?) complex file. With variable definitions it

Re: Fingering position in polyphony face to sharp glyph. Bug?

On 02.08.2018 12:10, Torsten Hämmerle wrote: I think this should get its own tracker issue. I created one and tried to include all the analyses yet presented. Best, Simon ___ lilypond-user mail

Re: Fingering position in polyphony face to sharp glyph. Bug?

Hi Harm, Yes, fingerings are quite a large construction zone (and right hand fingerings or string numbers as well). Issue 3692 hasn't been solved yet, and your examples show that there is also a general dot collision problem for right fingerings. When increasing snap-radius, fingerings may overla

Re: Fingering position in polyphony face to sharp glyph. Bug?

Simon Albrecht-2 wrote > I created one and tried to include all the analyses yet presented. > ; Thanks, Simon. I think makes sense trying to improve the fingering placement step by step. And everything that can get ...Orientations (fingeringOr

Re: layout of markup text (Peter Gentry)

The idea that included files are indistinguishable from copy-and-paste, even goes to extreme levels. This works: --- included.ly title = "title" composer = "composer" } -- --- main.ly \

Re: layout of markup text (Peter Gentry)

Noeck writes: > The idea that included files are indistinguishable from copy-and-paste, > even goes to extreme levels. This works: > > > --- included.ly > title = "title" > composer = "composer" > } > -- > > > --- main.ly

Re: Fingering position in polyphony face to sharp glyph. Bug?

Thomas Morley-2 wrote > […] > \mark "Fingerings right" > \set fingeringOrientations = #'(right) > […] Hi Harm, When setting fingeringOrientations to #'(right), the occasional collision of fingering and dots are a result of dots moving vertically away too far from their noteheads. In

partcombine for choir and piano?

Hi, reading about \partcombine recently stirs up some questions. I always considered it a tool for orchestra scores (violins of flutes). But perhaps it's not limited to that. My questions (and some short reasoning): 1. Does \partcombine make sense for combining *soprano and alto* into one staff

Re: partcombine for choir and piano?

On 02.08.2018 23:15, Noeck wrote: My questions (and some short reasoning): 1. Does \partcombine make sense for combining *soprano and alto* into one staff or should I use voices? I see pros (+) and cons (-): - The fact that I would prefer the 'apart' style everywhere makes me think that i

Re: Opinions: expressive text and markup sizes

Btw, the factor is probably 2^(1/6) ≈ 1.122462048309373 as Lilyponds scales the fonts in a way that 6 steps double the font size. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: partcombine for choir and piano?

Hi Simon, thanks for your helpful answer. Am 02.08.2018 um 23:37 schrieb Simon Albrecht: >> + The positioning of dynamics is better for partcombine. >> Why are all dynamics below the staff for the voices-setup by default? > I’m not sure what you mean. Here is what I mean: When I combine t

Re: partcombine for choir and piano?

Noeck writes: > Hi, > > reading about \partcombine recently stirs up some questions. I always > considered it a tool for orchestra scores (violins of flutes). But > perhaps it's not limited to that. > > > My questions (and some short reasoning): > > 1. Does \partcombine make sense for combining *

Re: partcombine for choir and piano?

On 8/2/2018 4:37 PM, Simon Albrecht wrote: On 02.08.2018 23:15, Noeck wrote: 1. Does \partcombine make sense for combining *soprano and alto* into one staff or should I use voices? I see pros (+) and cons (-):   - The fact that I would prefer the 'apart' style everywhere makes me     think that

Re: partcombine for choir and piano?

On 02.08.2018 23:58, Noeck wrote: There are two forte signs (one would be enough) below the staff (above would be better). I understand that I have to take care because of the lyrics. But why isn't the upper voices' dynamics above the staff - as \voiceOne does set the direction for so many other

changing symbols used by Measure_grouping_engraver

> > > > \version "2.19.81" %{ I wonder if anyone can point me in the right direction. I'd like to modify the sybols used by the Measure_grouping_engraver http://lilypond.org/doc/v2.19/Documentation/snippets/rhythms#rhythms-conducting-signs-measure-grouping-signs In particular, how to change t

Re: Interactive PDF Link to Notes in Preview

Il giorno gio 2 ago 2018 alle 9:28, Federico Bruni ha scritto: Il giorno lun 9 lug 2018 alle 7:26, Mats Behre <"mb.maillists"@gmail.com> ha scritto: My problem now is that SwiftDefaultApps silently fails to set this as the textedit target, possibly because my info.plist is too old