Source Serif Pro font baseline not consistent
I'm using Indesign 15.0 on MacBook Pro (Retina, Mid 2012) running Mojave version 10.14.6
I'm experiencing a bug with the Source Serif Pro font , which I use extensively in a particular project.
I open an existing document, and the text in Source Serif Pro looks as you'd expect it to. When I start to edit the text however, it all jumps down as if the baseline settings of the text frame has been changed (although checking in the settings confirms they haven't been).
Copying and pasting the frame, or the text into a new frame, doesn't help.
It only happens with Source Serif Pro (all weights) - if I change the font, even to other Adobe Fonts it doesn't happen. It also happens in new documents.
It may be worth mentioning that a colleague works on the same Indesign files on a PC (we share the files via Dropbox) but he doesn't experience the issue.
We both share another related bug with Source Serif Pro in that quotation marks just display as 'straight' even though 'use typographer's quotes' is turned on in preferences. This can't be fixed through the Glyphs panel either.
My feeling is it's something to do with this particular font being used a lot over 2 different platforms.
We are looking into the issue.
Seems there is some discrepancy in font information of the font present in Typekit and that on Google fonts.
gary b commented
Can confirm this is still an issue in 2023. Nothing like having it happen in the middle of a big, time-sensitive annual report project.
I have been suffering form this problem as well. I struggled to describe the problem until i realized it was ONLy this font and ONLY the Typekit version of this font. Open source was normal.
I have been encountering the same issue with Source Sans Pro from Adobe Typekit. However I do not get the problem when disabling it from Typekit and downloading it from Google Fonts instead - it works as it should do. So my thoughts is that its a Typekit/Indesign issue?
My work colleague also has the same issue. It only started happening 2 days ago - was completely fine before that.
Did you manage to fix it John?