Hi Octo,
I was just testing the "space height opacity problem" that you mention.
Could you tell me how you made it work with Maestro because I get the same opacity problem already in Maestro (which explains why it's partially the same in my fonts) ?
Maybe it's a difference between MacOS and Windows (I only tested on Windows) ?
This is what I get on Windows with Maestro and Times New Roman (i.e. the default fonts) when creating an opaque expression with "Enforce Minimum Width" set and height/width=0. "f" and two spaces are from "Maestro", "sub." is from "Times New Roman".
- opaque.jpg (122.56 KiB) Viewed 16406 times
If I remove the "Space" from Maestro (between f and sub.), it's still the same:
- opaque2.jpg (40.21 KiB) Viewed 16406 times
It's the "f"-height in Maestro which already leads to the opacity problem:
- opaque3.jpg (106.24 KiB) Viewed 16406 times
It seems to me that this is a Finale bug/feature. The opacity area in text expressions doesn't use the reduced boundaries of the FAN, but the default height of the font. So it's not a height problem of the "Space" symbol, but a height problem of the font.
And the only option to solve this would be to reduce the default height of the font to the same distance that Maestro has from its ymax/ymin to the maximum boundaries of the dynamics (i.e. the "f" for ymax, and the "p" for ymin). But if I do so, some symbols might be cut off in Finale, because their ymax is above the font's ymax, so this is no solution.
Example of symbol cropping because wrong font height:
- opaque4.jpg (112.57 KiB) Viewed 16401 times
Or am I missing something ?
Jan