I did some work on one Adobe account. Recently I had to switch accounts. On the new account, same PC, same fonts installed, when I click into documents I'd already created, the font Fira Sans now situates itself a noticeable distance from the top of the text box, knocking the next line of text off.
Specifically it's Fira Sans Book in these examples.
Any idea what's causing this? Everything has paragraph styles applied and no settings have changed at all, and no styles are being overwritten.
1 Correct answer
I used Google Open Sans in a previous brand and I couldn't redistribute it - always just had to send people to the download page anyway lol. Or Adobe Fonts. Afaik there were no issues from that though. I HOPE this kind of thing is rare!
For now, for this, I've switched to Meta Pro, also out of Adobe Fonts. Having been let down, I'm immediately back for more. All I know is I definitely don't trust Fira Sans to work consistently across users and machines, if I have this issue on the same PC after
...
15
Replies
Compare the two font versions, but I'm wondering if it isn't a Type Frame Options Offset setting. Or maybe the offset setting will take care of it.
~Barb
More info. I actually am still able to access my old account. I just signed into that one, opened my doc, and it's fine. I clicked in and made an edit and it didn't shift the baseline.
Signed out of that account, signed into my new one, and the issue reappears.
I clicked on Fira Sans Book in Find Font and got the "More Info":
The information is exactly the same on either account. I just don't get it. It's fine on one account, but not on another, while evidently using exactly the same font.
OK, one more thing. The screen cap above is from my old account. I looked at it again on my new account, and I'm seeing this:
I'm sure that info at the beginning has something to do with this. It's performing some sort of conversion.
Odd, when I load Fira Sans from Adobe fonts, I get a different version # than yours (4.301, as opposed to your 3.111).
That being said, this could be a font cache issue combined with a version issue.
Many of these "open source fonts" that both Google and Adobe Fonts offer tend to tinker with their outlines over time, including repositioning their ascender lines, and then release updated versions along the way, so the version you're loading from Adobe today may NOT be the one you used to create the document previously. Different ascender lines can very definitely cause different baselines depending on what version you are using and sometimes what source (e.g Adobe Fonts usually serves out Postscript-flavoured OTF while Google fonts are usually TrueType-flavoured... sometimes with differently-defined ascenders).
But since you've said you have only used the Adobe Fonts version, something else is at play, and my guess it's font cache.
When you created the document on one System, using an older version of the font that was being served at the time (e.g v 2.000), the font is cached by your System/Adobe apps, and it will reuse the font cache version whenever the font is requested going forward to speed up rendering. If you open the document on a different System, that System also creates a font cache version, using the currently available font (say v 4.000). So even if you've loaded the exact same version now, each System is going to use the existing cached version even if it's the same exact document.
What you can try is purge your font caches* on both machines and then try again and see if the difference still exists.
*if you use a 3rd party font manager they usually have a utility to purge font caches on an Application(Adobe) level and also System level. If you don't have one, you can still do it but it's more manual (you can find instructions by searching for "rebuild font caches")
example (this is FontExplorer X Pro):
It's a good maintenance routine to clear font caches from time to time anyway.
@John25589026ghrf said: "Unless anybody has any other ideas..."
Thanks John for the additional info where you compare the font Info of the two accounts. That's very important to know! Obviously Adobe changed the font version from 3.111 to 4.301! Perhaps your old account still has the old font version cached on your system? Something like that… ?!
This seems to be a new facet what can happen with activated fonts from Adobe Fonts.
Did a test and activated Fira Sans Book the first time on my machine and the version number clearly says 4.301.
From my German InDesign 2022 version 17.3.0 on Windows 10:
Hm…
To avoid the shifting of the baseline I see only one remedy:
Do not base the first baseline on Ascent, but to something else! Cap Height could be the solution.
That has helped in other cases. Unfortunately Ascent is InDesign's default…
I would also raise the issue at the Adobe Fonts User Forum:
Also note, that on Google Fonts there is no Book style for Fira Sans.
So my assumption was wrong that there perhaps was a mix of Adobe Fonts and Google Fonts.
It's just an issue between two different versions of the same font with Adobe Fonts and InDesign's bug with the first baseline setting for text frames.
Regards,
Uwe Laubender
( Adobe Community Professional )
AdChoices