Am So., 23. Feb. 2020 um 16:52 Uhr schrieb David Kastrup <d...@gnu.org>: > > Thomas Morley <thomasmorle...@gmail.com> writes: > > > Hi, > > > > consider the following code > > > > \version "2.19.84" > > \markup \dynamic { s f m z p r } > > > > output attached. > > > > And compare with the output of > > > > \version "2.19.84" > > { R1 } > > \markup \dynamic { s f m z p r } > > > > The markup does not use the same font (from visual inspection). Most > > noticeable with "z", but the others are slightly off as well. > > > > No clue whats happening here... > > It happened somewhere between 2.19.25 and 2.19.26 > > > > Also > > { > > \override DynamicText.stencil = > > #(make-stencil-boxer 0 0 ly:text-interface::print) > > c'2_\f > > } > > shows significant differencies for 2.19.25 and 2.19.84, attached as well. > > This one leads to changed appearance for combined dynamics like mf, > > sfz and the like. > > The mf directory shows the following commits in that version range: > > commit 2ce9d3b0ac456df77a73342fdf802f2e198c3b4e > Author: Masamichi Hosoda <truer...@trueroad.jp> > Date: Fri Aug 14 22:45:20 2015 +0900 > > Issue 4552 / 5: Remove makefiles to convert and install URW++ fonts > > This commit removes makefiles to convert to OTF and install URW++ fonts. > (Century Schoolbook L, Nimbus Sans L, Nimbus Mono L) > > commit bb66d05c73dbc038b994430545c85966fd9edc12 > Author: Masamichi Hosoda <truer...@trueroad.jp> > Date: Fri Aug 14 20:11:33 2015 +0900 > > Issue 4552 / 3: Replace LilyPond default font to TeX Gyre fonts > > from to > Century Schoolbook L -> TeX Gyre Schola > Nimbus Sans L -> TeX Gyre Heros > Nimbus Mono L -> TeX Gyre Cursor > > commit 7c30014f110ee407b56c91d3b451b28ce7a89f8a > Author: Masamichi Hosoda <truer...@trueroad.jp> > Date: Mon Aug 10 10:47:49 2015 +0900 > > Issue 4552 / 2: Add makefiles to install TeX Gyre font OTF files > > This commit adds makefiles > to install TeX Gyre font OTF files. > > commit ebd5a4af248c95178abb8490a32c0b8d3af4e1d7 > Author: Masamichi Hosoda <truer...@trueroad.jp> > Date: Sat Aug 8 21:15:37 2015 +0900 > > Issue 4544 / 3: Fix makefiles for LilyPond local fontconfig conf file > dividing > > This commit fixes LilyPond local fontconfig conf file dividing. > > commit 0fbbdc6c58432060770d3d4f76e063c2028c0023 > Author: Masamichi Hosoda <truer...@trueroad.jp> > Date: Sat Aug 8 19:06:50 2015 +0900 > > Issue 4544 / 2: Fix LilyPond default fonts definition > > Due to conf file loading order, generic font aliases > `serif', `sans-serif', 'monospace' were unavailable > in LilyPond default fonts definition. > So the glyphs that are not contained > in the list of font definition, > like Japanese glyphs were used unexpected font. > > This commit changes > LilyPond default fonts definition loading order > for enabling the aliases. > > > There will probably be a few more commits outside of the mf directory > that belong to the same issues. > > Could any of those commits have an effect like that? Would that likely > show just on one particular computer, or might other systems also be > affected? > > Hosoda-san, do you have any idea here? > > Thank you > David > > -- > David Kastrup
Looks like LilyPond was confused by several fonts in several folders. See: https://lists.gnu.org/archive/html/lilypond-user/2020-02/msg00389.html While this is my own fault, I still think LilyPond should be more robust in this regard. I.e. always use emmentaler, unless explicitely specified differently. Cheers, Harm _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond