Hello, I just had something odd happen. I have been working with Century Expanded as my lyric font. It was displaying correctly except for this weird issue with hyphens sitting too high when the lyrics were italicized. I thought the issue originated from having multiple files of the font. So I cleared them all out and re-downloaded the font. Now, both the regular and italicized versions of the font appear drastically compressed width-wise. I opened up a Pages document to see if the font displays the same in other applications, and it appears normally there. Is this a Dorico issue, or is it a setting I’m overlooking?
Here’s a couple of screen shots to show what I’m talking about. The first is a screen shot in Dorico. v. 1 is Century Expanded and the chorus line is Century Schoolbook just for comparison. The second screen shot is from a pages document with the top line being Century Expanded and the bottom line being Century Schoolbook. The font settings in both are the same, but for some reason, Dorico is not displaying the same way Pages does.
1 Like
You’re sure the Paragraph Styles are identical? No “Stretch” value set?
And you’ve restarted the computer?
FWIW, Century Expanded (LT Std) works fine for me.
Are you using a free version of Century Expanded or the commercial Monotype one? Free fonts sometimes have the disadvantage that the metrics are not quit right - or they are just stolen!
It’s possible Dorico is not handling the font metrics for that font the same as in the past, although only @dspreadbury could comment on such matters.
Your top image look s like a font substitution has occurred - does not look like Century to me. Appears to be English chars from an Asian font. Are you running a non-English OS?
No stretch value is set.
I’ve not tried restarting my computer. It had been handling the font just fine overall, I just noticed an issue with hyphens. But I did have a free version of the font downloaded so I thought maybe that was the problem. I cleared it all out and re-downloaded the font folder and now all of a sudden it doesn’t look remotely the same. I restarted Dorico itself, I updated Dorico, and nothing changed.
I will try restarting the computer next.
Update: Restarting the computer did not work.
I had been using a free version but lately have been using the Century Expanded by URW that I purchased. But when I did that, the free version was still there I think, which I thought was creating the little quirk with hyphens when using the italicized font. I am using Sonoma MacOS.
It’s not impossible that the font is being handled differently by the current version of Dorico than it was being handled in earlier versions. Dorico’s view onto the world of fonts is mediated by the Qt application framework. Dorico 5 and Dorico 3.5 are several versions apart in terms of Qt, so it’s certainly possible that the font is being treated differently now. If you want to zip up the fonts themselves along with a simple test project and email them to me at d dot spreadbury at steinberg dot de, I can take a look.
1 Like
I emailed those to you (assuming I entered the email correctly). But let me know if you don’t receive them or if you need something else sent.
Thanks for sending the font over to me, Coulter. I’ve spent a few hours looking into what might be going on here, but so far to no avail. I will ask one of my colleagues who is more expert than me in the intricacies of font handling to take a look, but I can’t promise that we’ll have an answer for you immediately.
In the meantime, I don’t think you will have any option but to consider an alternative font.
@Coulter_Teel did you make sure Dorico was completely closed when you removed the old font and installed the updated version? I have found font caching issues from time to time if I add or remove fonts when Dorico is launched.
If that’s a possible pulprit, I think you should clear the font cache. I recall having to do this a few times (it was a pain in the neck).
Thanks for the suggestion, Dan, but in this case I believe the problem is in Dorico somewhere, rather than relating to the font itself.
I don’t think it was completely closed when I removed the font files and updated. I know dspreadbury didn’t think that was the problem, but I went ahead and tried clearing the font cache just to make sure. Unfortunately, it did not change anything.