lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: rendering differences if using `-j12 CPU_COUNT=12`


From: Thomas Morley
Subject: Re: rendering differences if using `-j12 CPU_COUNT=12`
Date: Sat, 1 May 2021 16:35:42 +0200

Am Sa., 1. Mai 2021 um 12:25 Uhr schrieb Thomas Morley
<thomasmorley65@gmail.com>:
>
> Am Sa., 1. Mai 2021 um 11:47 Uhr schrieb Jean Abou Samra <jean@abou-samra.fr>:
> >
> >
> > Le 01/05/2021 à 11:33, Thomas Morley a écrit :
>
> > >> Wouldn't it be better to _not_ reset
> > >> `standard-alteration-glyph-name-alist' at all?
> > >> The files hel-arabic.ly, turkish-makam.ly and makam.ly all define some
> > >> custom-makam-glyph-alist and use this alist in \layout for
> > >> KeySignature, Accidental, AccidentalCautionary, TrillPitchAccidental,
> > >> AmbitusAccidental.
> > >> Is this not sufficient? In other words why not simply delete all
> > >> occurrencies of:
> > >> #(set! standard-alteration-glyph-name-alist
> > >>         (append whateverMakamGlyphs
> > >>                 standard-alteration-glyph-name-alist))
> > >> ?
> > >> Then we would rely only on the mechanism partially demonstrated in
> > >> input/regression/accidental-ancient.ly
> > >>
> > >> I'll test that later this WE
> >
> > It's slightly more complicated. Chord names use the
> > alist directly (sigh):
> >
> > (define-public (alteration->text-accidental-markup alteration)
> >    (make-smaller-markup
> >     (make-raise-markup
> >      (if (short-glyph? alteration)
> >          0.3
> >          0.6)
> >      (make-musicglyph-markup
> >       ;; FIXME -- use current glyph-name-alist here.
> >       (assoc-get alteration standard-alteration-glyph-name-alist "")))))
>
> I've never seen arabic, turkish etc chords.
> Do they exist in the same manor as in western music?
> I really don't know, can't judge.

Ok, I'm obviously wrong.
See input/regression/note-names-makam.ly

>
> >
> > and the markup commands \sharp et allies do the same.
>
> My concern is already how to deal with
> standard-alteration-glyph-name-alist in the _same_ file (not only in a
> row of multiple files).
> As soon as standard-alteration-glyph-name-alist is changed \sharp et
> allies will not render as before anyway.
>
> Happens already for:
> #(set! standard-alteration-glyph-name-alist
>   (append alteration-hufnagel-glyph-name-alist
>           standard-alteration-glyph-name-alist))
>
> \markup { \doubleflat \flat \natural \sharp \doublesharp }
>
> I can easily imagine some educational text listing accidentals in
> western music, arabic music , etc.
> The predefined markup-commands for accidentals wouldn't be of much use.
> One would need to fall back to \musicglyph anyway.
>
>
> Cheers,
>   Harm



reply via email to

[Prev in Thread] Current Thread [Next in Thread]