Font issues - Roboto for sure

[kaiserwilhelm]

Been using Universal Type Server since before it was even named that.
Customer collects components. We put into UTS under a job number.
Past six months more and more and more packaging not going right.
Customer used Roboto Medium
Customer tells INDD to collect
Roboto Medium Regular gets packaged.
Customer does not have Roboto Medium on in the Cloud.
Any ideas?
So bad that if all fonts are off on UTS and I go to the packaged folder with Document Fonts, etc
and double click the INDD - it does not find the font!

 

[chriscozi]

YES -Adobe has really screwed this.
They are FORCING INDD to use cloud fonts.
Even if they are loaded locally.
Sigh.
COMPLAIN TO THEM ! ! !

 

[Dov Isaacs]

Actually, this is not true at all! Adobe is absolutely not forcing you (or anyone else) to use “cloud fonts.”

If you unconditionally don't want to use the Adobe Fonts service, simply turn it off in the Creative Cloud Desktop Application.

In the case of the Roboto fonts, install those fonts locally on your system (whether it be Windows or MacOS). If you are using some third party font manager, make sure that it has those fonts activated. But in no case should you activate the Roboto fonts with the Adobe Fonts service if you subsequently want to use them locally.

What I suspect is happening is that @kaiserwilhelm's customer may have activated the Roboto fonts via the Adobe Fonts service and then installed the fonts locally. If both are available (or if the Adobe Fonts version was activated and Adobe Fonts is still enabled), and InDesign previously used the Adobe Fonts version, InDesign uses the Adobe Fonts version.

The same issue probably occurs with Illustrator as well.

Is this intuitive, no! Can it be improved, yes! And the issues are particularly problematic if you effectively have multiple font managers running in parallel.

- Dov

PS: Remember that font is a four letter word beginning with an f.

 

[chriscozi]

Actually, this is not true at all! Adobe is absolutely not forcing you (or anyone else) to use “cloud fonts.”

If you unconditionally don't want to use the Adobe Fonts service, simply turn it off in the Creative Cloud Desktop Application.

There is the word. "Unconditionally."

Do we understand that either you use Adobe Font Service or you don't?
Of course we do.
We deal with Designers using Adobe Font Service continually.

What we DON'T understand is the behavior of the Adobe application REFUSING to recognize locally loaded fonts UNLESS you turn off the Adobe Font Service.

Not so subtly it should be known as the "Adobe Font Hostage Service."

In the case of the Roboto fonts, install those fonts locally on your system (whether it be Windows or MacOS). If you are using some third party font manager, make sure that it has those fonts activated. But in no case should you activate the Roboto fonts with the Adobe Fonts service if you subsequently want to use them locally.

What I suspect is happening is that @kaiserwilhelm's customer may have activated the Roboto fonts via the Adobe Fonts service and then installed the fonts locally. If both are available (or if the Adobe Fonts version was activated and Adobe Fonts is still enabled), and InDesign previously used the Adobe Fonts version, InDesign uses the Adobe Fonts version.

So yes the Adobe application chooses the Adobe Font Service version over the local font version.
And yes I can confirm that you can get the local version to work IF you turn off the Adobe Font Service.

The same issue probably occurs with Illustrator as well.

Is this intuitive, no! Can it be improved, yes! And the issues are particularly problematic if you effectively have multiple font managers running in parallel.

But let's blame all those third party applications! Even those darn MULTIPLE third party applications.
(grumble grumble what's wrong with our font manager application?)
Poor little Adobe applications get confused!
With their 'own' API's in charge of the process.
You might disagree about that.
Just ask Apple and Microsoft who has 'mandated' or 'requested' the changes to their font handling API's for the last twenty years and how those Font Management applications have had to dance to the Adobe tune.
We all know who is the 800 pound gorilla in this room.

- Dov

PS: Remember that font is a four letter word beginning with an f.

Rich! (snark intended).
I'll stop trolling now.