Phil Holmes wrote: > OK. You're definitely attaching cropped screenshots, > AFAICS.
Yes. > Compare the first one you attached, where the heading > "Using \lyriscto" is sans serif, with the one you've just > attached. That's a serif font. Exactly. In the first one, I set my browser's default font to sans-serif. In the second one, I changed my browser's default font to serif. > So, to me, your system, for whatever reason, is struggling > to find the right fonts. No. My browser is displaying the fonts I request, consistently. > In the first screenshot, your browser has failed to find > the correct font. No. For that screenshot, I had set my browser's default font to sans-serif, and then my browser displayed the text in a sans-serif font, so my browser *succeeded* in finding the right font. > In the second, it's OK. Yes, because that time I had set the default font to serif. > Perhaps simply remaking the docs will fix it. I hope not! :) That would make this bug extra hard to track down. Far better for it to be consistent. I can try that, but I don't really think that will help. > Whatever it is, it's not a problem with the lilypond code, > as Colin and I can attest. Personally, I wouldn't be so quick to make that conclusion. Hypothetically, if a new LilyPond release completely failed to work on Mac and Windows, but continued to work for you and Colin, I don't think you'd say there's no problem with the lilypond code. In any case, does anyone have any suggestions for troubleshooting this? Thanks - Mark _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
