Re: markup font bug

2007-02-27 Thread Mats Bengtsson
Graham Percival wrote: Dan Eble wrote: % Note the missing flat in the markup. % Should \flat use the flat sign from Lilypond's font, % or is this something I'm not supposed to want to do? I'd call it a missing warning. Try this: bf1^\markup{ \override #'(font-name . "Courier")

Re: markup font bug

2007-02-26 Thread Graham Percival
Dan Eble wrote: Thanks for the reply, but because the example is intentionally simple, the simple workaround is unsatisfying. Imagine this fragment as part of bookTitleMarkup in an include file: Why not define myFlat = \markup{ \normal-text { \flat } } and then do \header = { instrument =

Re: markup font bug

2007-02-26 Thread Graham Percival
Dan Eble wrote: % Note the missing flat in the markup. % Should \flat use the flat sign from Lilypond's font, % or is this something I'm not supposed to want to do? I'd call it a missing warning. Try this: bf1^\markup{ \override #'(font-name . "Courier") { Ceci n'est pas une B

Re: markup font bug

2007-02-25 Thread Mats Bengtsson
When you explicitly specify the font-name property, you override normal font selection mechanism. For example, the markup command \flat internally uses the property font-encoding to select the music font, but as you have noticed, this doesn't work if the font-name property has been explicitly sp

markup font bug

2007-02-25 Thread Dan Eble
% Note the missing flat in the markup. % Should \flat use the flat sign from Lilypond's font, % or is this something I'm not supposed to want to do? \version "2.10.19" \include "english.ly" \score { \relative c'' { bf1^\markup{ \override #'(font-name . "Courier") { Ceci n'est pas