Re: 2.25.16 D.S. al Fine

2024-06-08 Thread Paul Scott
Ok, I did find the solution someone gave me some time ago.  I still wonder: 1. Why the default uses the redundant \segnoMark. 2. Why there isn't a more direct option for what I believe is the more common notation. Paul On 6/8/24 11:42 PM, Paul Scott wrote: Using the repeat segno structure h

2.25.16 D.S. al Fine

2024-06-08 Thread Paul Scott
Using the repeat segno structure how can I eliminate the redundant segno mark in D.S. [segnoMark] al Fine ? I can't quickly find any examples in printed music that has the redundant segno mark.  D.S. aleady means "dal segno" or "from the sign." I don't have a copy of Gould but Wikipedia and

Re: Two adjacent clefs

2024-06-08 Thread William Rehwinkel via LilyPond user discussion
Dear Richard, I'm not sure what you mean, but I think I would do something like this for putting multiple clefs together. -William % -- \version "2.25.16" \relative c' { \override Staff.Clef.stencil = #ly:text-interface::print \override Staff.Clef.text = \markup { \raise

Re: Two adjacent clefs

2024-06-08 Thread Richard Shann
On Sat, 2024-06-08 at 08:09 -0700, Knute Snortum wrote: > On Sat, Jun 8, 2024 at 7:03 AM Richard Shann > wrote: > > I think it's not uncommon for two clefs to appear side by side at > > the > > start of a piece (e.g. when a piano piece starts with both staves > > in > > bass clef so as to alert th

Re: Two adjacent clefs

2024-06-08 Thread Knute Snortum
On Sat, Jun 8, 2024 at 7:03 AM Richard Shann wrote: > I think it's not uncommon for two clefs to appear side by side at the > start of a piece (e.g. when a piano piece starts with both staves in > bass clef so as to alert the pianist that the upper staff is not in > treble clef). > How is this do

Two adjacent clefs

2024-06-08 Thread Richard Shann
I think it's not uncommon for two clefs to appear side by side at the start of a piece (e.g. when a piano piece starts with both staves in bass clef so as to alert the pianist that the upper staff is not in treble clef). How is this done in LilyPond? Richard Shann

Re: Regular Polygons

2024-06-08 Thread Werner LEMBERG
> Thankfully, it should be trivial to make the changes. The question > now is what reference glyph is the best? If you have an argument, the shape should enclose it symmetrically (more or less) – it is up to you how sophisticated the algorithm is to do that in the visually most pleasing way (i.

Re: Regular Polygons

2024-06-08 Thread Shane Brandes
Typically fonts use x-height as a general design parameter. I don't know if you find that helpful in this interesting project, but it is a point of possible useage. Regards, Shane Brandes On Sat, Jun 8, 2024, 5:47 AM Aaron Hill wrote: > Thank you both, Werner and Valentin, for taking the time t

Re: Regular Polygons

2024-06-08 Thread Aaron Hill
Thank you both, Werner and Valentin, for taking the time to look at my submission. When I was playing around with drawing shapes, I was thinking paper scale not text scale. This was inspired by Paolo's desire to draw arbitrary arrows and things. Because of that, I presumed the end user woul

Re: Regular Polygons

2024-06-08 Thread Werner LEMBERG
> I was playing around with drawing regular polygons, which led to > creating a new markup command with several configurable options. > (Some of these options are inherited via the built-in \polygon > command.) > > There might be a few things to tighten up, but I believe it is in a > pretty work

Re: Regular Polygons

2024-06-08 Thread Valentin Petzel
Hello Aaron, I would think there is little actual need to specify the size as parameter. After all, you have the font-size proportion, using which you can control size by \fontsize ... You’d simply need to replace size by (magstep font-size). Alternatively if you want to match text you could i