Re: Reminder: Some chord symbols still broken in 2.5.19

[Matthias Neeracher]

On Apr 15, 2005, at 2:20 AM, Han-Wen Nienhuys wrote:

> On Fri, 2005-04-15 at 00:55 -0700, Matthias Neeracher wrote:
>
> > [Since we seem to be moving towards a release candidate, I thought
> > I'd repost this bug report. This is the one issue that currently
> > keeps my on 2.4.x for my personal needs.]
> >
> > On MacOS X, it seems that the symbols for x:maj7 and x:m7.5- still
> > don't work properly in 2.5.19 (The former is omitted, the latter
> > printed as a long box).
> > Is this a known bug or is it a platform specific problem?
>
> This is font related problem.  Lily uses Unicode codepoints, and lets
> pango decide which symbol to use. At the moment, Greek Capital  
> Delta is
> used for the white triangle, from chord-modifier-init.ly:
>
>         whiteTriangleMarkup = \markup {
>           %%  394 capital delta
>           #(ly:export (ly:wide-char->utf-8 #x0394))
>
>           %% 2206 : delta from the symbol font.
>           %   #(ly:export (ly:wide-char->utf-8 #x2206))
>
>           %% up pointing triangle
>           % #(ly:export (ly:wide-char->utf-8 #x25B3))

None of these variants show up, and neither does the #x00F8 for  
the .m7.5-, although all of these characters are supported in dozens  
of fonts.

> Pango should select a font that contains these glyphs.

I'm afraid I'm not all that familiar with pango. Are there any debug  
environment variables that I could set to trace pango, or any  
suggestions what API call I should intercept to see when it's looking  
for these characters.

> Can you verify that the standard Mac fonts do not cover these  
> codepoints?

They do.

> I see two options:
>  - draw a triangle by hand (robust)

But probably not very extensible to other font styles.

>  - making sure that a font with appropriate glyphs is installed.

It would seem to me that that should be the proper resolution.

Matthias