Jean Abou Samra wrote:
[Robin]
The stroke width I see is 1px (Firefox at 100%). This makes the
stroke dominated by edge effects; the surrounding white dilutes its
colour.
Do the WCAG recommendations recognise this? If not, please don't
apply their levels to this case.
I don't know. I am
Oops, successive redundant *chords* with a changing bass note, I meant to
say.
LT
Harm,
Thanks so much for sharing and tightening up this code for hiding redundant
bass notes in successive slash chords, and thanks Elaine Alt for initiating
the thread. It's a really useful feature to have in a le
Am Di., 4. Jan. 2022 um 20:52 Uhr schrieb jerome talkington
:
>
> Harm,
>
> Thanks so much for sharing and tightening up this code for hiding redundant
> bass notes in successive slash chords, and thanks Elaine Alt for initiating
> the thread. It's a really useful feature to have in a leadsheet,
Thanks again!
On Wed, Jan 5, 2022 at 5:31 AM Thomas Morley
wrote:
> Am Di., 4. Jan. 2022 um 20:52 Uhr schrieb jerome talkington
> :
> >
> > Harm,
> >
> > Thanks so much for sharing and tightening up this code for hiding
> redundant bass notes in successive slash chords, and thanks Elaine Alt for
On Sat 01 Jan 2022 at 22:27:31 (+0100), Valentin Petzel wrote:
> May I just fan the fire by saying that on kde this works out of the box?
>
> That being said, the only really usable pnc implementation is Frescobaldi, as
> that one will keep track while you’re editing the file and thus always poin
The fingering here collides with the tempo. If the cross-staff beams are
commented out (all notes on the upper staff), the fingering displays fine.
Is there a workaround? Am I doing something wrong?
\version "2.23.5"
global = {
\time 6/8
\tempo "Allegro"
}
goUp = { \change Staff = "right"
Le 05/01/2022 à 20:59, Michael Rivers a écrit :
The fingering here collides with the tempo. If the cross-staff beams
are commented out (all notes on the upper staff), the fingering
displays fine.
Is there a workaround? Am I doing something wrong?
\version "2.23.5"
global = {
\time 6/8
\t
On Tue, 21 Dec 2021, Valentin Petzel wrote:
Hello,
Hello Mike,
Guile 1 to Guile 2 did change some syntax and some mechanics, which means that
guile code must be reworked for guile 2 and using guile 2 makes the program
much slower. There is ongoing long time effort to port Lilypond to guile 2
A nice thing I’ve discovered in reviving my old (2.18) project is that
articulate.ly now expands repeats without `\unfoldRepeats`. A less-nice
thing is that this behavior behaves oddly around `\alternative`:
\version "2.23.5"
\include "articulate.ly"
music = \relative c' {
Hi;
Musical question here, not specific to Lilypond.
I have an excerpt that I am engraving as a sample which uses the dynamic "sf".
In the Wikipedia article
https://en.wikipedia.org/wiki/List_of_musical_symbols
"sfz" is mentioned but not "sf".
Ah, I see in my printed Norton/Grove Conc
10 matches
Mail list logo
