How do I get rid of Typekit

Report · Feb 01, 2014

Every time I open an old indesign file. I am getting a window for typekit. I use suitcase and all the fonts are located there. Not installed on my computer. (I have 9800 fonts so you get the idea).

It will not find my suitcase fonts even if they are open - I need it off ASAP any help will be appreciated.

Report · Jan 21, 2015

I am having this problem with Illustrator CC 2014. Is there an update coming to FontExplorer? I can't actually use any of the fonts managed by it. FontExplorer X has activated the font but Illustrator can't see it.

Report · Jan 21, 2015

Ask FontExplorer tech support about FontExplorer updates and problems.

Also, this is the InDesign forum, not Illustrator.

Report · Jan 21, 2015

Kind of the same issue for all Adobe products, and both programs were mentioned in this discussion. This issue arose because of Adobe not because FontExplorer did anything.

Report · Jan 21, 2015

But well designed plugins also have to keep up with changes in the software they're plugged into.

And that's not Adobe's fault.

Report · Jan 21, 2015

That may well be, but there are people in this thread, myself included, who don't use third party font managers nor want Typekit's intervention.

And before you repeat it: No, turning it off in the CC widget does NOT stop Illustrator interrupting me with an uneeded and unwanted Typekit missing fonts warning.

That is ‘Adobe's fault’.

Report · Jan 21, 2015

So what your saying is any 3rd-party Type Management software has to be like an anti-virus program and battle everything Adobe throws at them?!

I could see if it were an interface issue, or the 3rd-party software needed to adjust programming code... but this is like Microsoft putting their Internet Explorer in place of your favorite browser because you updated operating systems! ... and I believe Microsoft was fined in that case!

Report · Jan 21, 2015

Ask any developer. They run into this all the time. An extension developer for Chrome, or Internet Explorer or Safari has to adapt to changes in that browser. A plug-in developer for an Adobe application has to deal with any changes Adobe throws at them, or they're stuck only supported older software. It comes with the territory.

Report · Jan 21, 2015

So you're saying a plug-in developer has to deal with a company inserting their own competing plug-in that disables and/or steps in front of the 3rd-party plug-in?! You are obviously not seeing our point. Font Explorer works just fine, it just doesn't work with Adobe putting their plug-in in front of theirs... and then MAKE IT IMPOSSIBLE TO DISABLE!!!

Report · Feb 11, 2014

QUESTIONS

1 - Where does Typekit reviece it's "instructions" from?

2 - Where can we turn this OFF?

3 - If this is not possible, how do we remove TypeKit altogether from within out CC Desktop App (or our desktop machines) so that we do not get this issue?

4 - I've also sent this info on to FontExplorer also... but have not heard back yet.

1. Typekit recieves the fonts from the current state of the machine. If a document uses fonts that are missing in it (InDesign Document), it simply checks for the presence of these fonts on Typekit (since not all fonts are present on Typekit we first check for the presence of fonts and then give the option to the user to either download them or Not).

2. You can turn the fonts syncing off from the Creative Cloud Preferences. BUT this would not step InDesign from sending the search request to Typekit for the presence of fonts, it is ONLY the downloading of these fonts that user has control over. You do not ideally need to do this since you can chose NOT to sync fonts from Typekit from the InDesign missing fonts dialog and the CC App will not do anything.

InDesign's missing fonts dialog has always been there, there have been some UI changes to it which show you the presence of Typekit.

Be rest assured that InDesign\CC app will NOT download any fonts to your system without your consent.

You have also mentioned that

The third (possibly not final) issue here is that this now causes a conflict with FontExplorer X Pro on out client machines, where it does not seem to recieve the request to activate before Typekit kicks in, so our fonts do not seem to autoactive smoothly anymore

This is one thing that i will need to get more info on. How did this work in previous versions of InDesign. Did Font Explorer X Pro download\activate the fonts that were missing automatically using Font Ex.

At what point does Font Explorer do this?

Sorry for the incovenience

Thanks & Regards

Javed

Report · Feb 12, 2014

I don't know about FEX, but Suitcase Fusion 5 does manage Typekit fonts.

Report · Feb 12, 2014

The third (possibly not final) issue here is that this now causes a conflict with FontExplorer X Pro on out client machines, where it does not seem to recieve the request to activate before Typekit kicks in, so our fonts do not seem to autoactive smoothly anymore
This is one thing that i will need to get more info on. How did this work in previous versions of InDesign. Did Font Explorer X Pro download\activate the fonts that were missing automatically using Font Ex.
At what point does Font Explorer do this?

I don't pretend to be completely across how and when the Font Explorer plugins work, but if I opened a file in PS, AI or ID which contained fonts which weren't currently activated then the respective FEX plugins would automatically find and open the necessary fonts. Note that it does not download fonts from an external source, it simply activates fonts already in my catalogue. Upon closing the file (or possibly the app - I don't recall exacty) those fonts would automatically be deactivated.

Now however the Typekit dialogue interrupts this process, and after I dismiss the Typekit modal window I need to manually activate the fonts in Font Explorer.

Note that this is only the perspective of a single person operation, opening almost exclusively files which I had created myself. And as I noted in my first comment, I've never satisfactorily understood how FEX and OSX work - frustratingly I invariably end up with hundreds of fonts permanently installed, presumably by apps, which I never had any input into. Currently I have many many Asian and Middle Eastern fonts installed, which I suspect has come about because I have opened files from a Chinese supplier in AI and Acrobat.

Report · Feb 12, 2014

This sounds more like an FEX problem. Have you contacted them?

Report · Feb 12, 2014

I concur, Bob. I think I said this earlier on, but I think the problem is that FEX hasn't been updated to account for Typekit yet.

The only people complaining are using FEX. We would have been innundated with problem reports if it involved other font managers as well.

Report · Feb 12, 2014

In fairness, it’s becoming increasingly difficult for third party developers to keep up.

That said, they’re either going to have to figure out a way or those that do keep up with eat their lunch.

Report · Feb 12, 2014

So - we've had a busy week here, so I'm a little slow getting back in. We've now got an update for FEX coming through (v4.1.1), but I've not had enough time this week to roll that out. We'll do that over this weekend. Hopeully that will assist somewhat. I'll report back first thing net week. Cheers.

Report · Sep 15, 2014

While the claim that the "missing fonts" dialog always came up is true, that was always the trigger for font activation through FEX plug-ins. The dialog would come up, the plug-in would launch the FEX interface, the fonts would activate automatically (where able).

_Now_, all of that is pre-empted by the Typekit dialog. Font auto-activation doesn't occur.

What I don't want is a designer activating and converting to TK fonts when their licensed OT fonts are just not activated.

And, to be perfectly clear, *we do _not_ want Typekit fonts.* We already have licenses for all of the Adobe Type Library. That should suffice. I do *NOT* want to be creating content the future use of which requires a perpetual subscription license.

Report · Sep 15, 2014

Agreed! My customers have sent licensed fonts with their files to me, and I want Font Auto Activation to activate exactly those!

Report · Sep 15, 2014

Have you checked with the FEX people. I’m using Suitcase Fusion and while the TypeKit dialog does pop up, it doesn’t stop SF from autoactivating my fonts.

Report · Sep 15, 2014

Bob, yes, I'm going through channels to see if there's an updated plug-in.

And it's exactly that pop-up dialog that I want off. I support a massive user base that's already leary of warnings and dialogs and new versions and features and more stuff to learn in applications they've been making their living with for years. While I myself may find the Typekit dialog merely annoying, I'm about to have a dozen design groups all demand that dialog go away. Right now my only answer is, "Adobe won't let me," and that doesn't help with adoption from a user base that's already experiencing upgrade trauma.

If Adobe wants more enterprise users to be pleased with the upgrade process, Adobe needs to get things like this out of enterprise users' faces.

Report · Sep 15, 2014

I agree that it should be a preference, but telling me won’t help.

Make your voice heard here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Be sure to state how this will benefit the majority of users

Report · Sep 16, 2014

to be honest, Bob, I wasn't posting on an Adobe forum expressly to get the opinions of others, expert though they may be.

Report · Sep 15, 2014

Hi All,

Let me make one thing clear here, its not a Typekit Dialog but the same Missing Fonts dialog that has always been there. Yes this does do an additional functionality of checking for the missing fonts in the document on Adobe Typekit and then only will it give you an option to Sync those Fonts. The checking part is currently not a user choice, but it does not do anything on other than that and until you take further action nothing will happen. We do have the request for making the checking part also a user chose and we are currently investigating the possibilities for the same.

The missing fonts dialog comes only when there are some missing fonts in the document, if FEX or Suitcase fusion were able to auto-activate a font that dialog would not have come up.

Regarding the Font Management softwares not being able to auto activate the fonts, I have tried with both the softwares mentioned here (Font Explorer Pro & Suitcase Fusion, there latest releases) and for me there was a problem with them earlier but working with the latest plugins they worked fine and auto-activation was successful (i tried with InDesign CC 2014).

It would be nice if you could also mention the actual version of FEX (and of InDesign also) you are using which is giving you the problem.

Thanks

Javed

Report · Sep 16, 2014

Hi, Javed,

Sorry, but no, it is decidedly not the same missing fonts dialog. There is a big Typekit banner at the top, and an error prompt to log in to Creative Cloud. (We work in an enterprise environment. We do not have individual CC accounts.) It needs to be manually dismissed before proceeding.

The previous missing fonts dialog was only seen if one's fonts were not activated by one's third-party font manager's auto-activation feature.

Now there is a prompt to activate them through Typekit, which can confuse less rigidly-thinking artistic folk, and an error message, further adding to the confusion, and an additional prompt to dismiss the dialog, before activation is to happen automatically. Ideally the file should just open. That's why we have auto-activation. This is a wall that gets in the way of seamlessly working.

I want it to not try to go through Typekit. Not at all. Ever. We don't use it. We've already paid for licensing thousands of fonts from houses that are not Adobe. We want our designers to use those.

What you've done is the equivalent of a shareware ad banner, prompting us to upgrade to the "paid" version to get rid of the ads. Only this is the paid version. You want to advertise your new product to me, find other methods than getting in the way of my work.

Report · Sep 16, 2014

"Sorry, but no, it is decidedly not the same missing fonts dialog. There is a big Typekit banner at the top, and an error prompt to log in to Creative Cloud. (We work in an enterprise environment. We do not have individual CC accounts.) It needs to be manually dismissed before proceeding."

Yes it has a Typekit banner on it, which is causing confusion here, and is giving the Sign In to CC prompt, but the fact the this dialog needs to be manually dismissed was true for the missing fonts dialog prior to Typekit Integration also.

"The previous missing fonts dialog was only seen if one's fonts were not activated by one's third-party font manager's auto-activation feature."

Yes this was the case, and this is the case now also, this dialog will come up only when there are missing fonts on ones system, whether some third party plugin is involved or not. Yes I agree that now auto-activation feature is not working could be because of this dialog or some other changes made to InDesign. This is the change that is causing the major problem here. I on my end have tried this multiple times and with the latest version of Font Explorer Pro and Suitcase Fusion am not facing this issue.

"Now there is a prompt to activate them through Typekit, which can confuse less rigidly-thinking artistic folk, and an error message, further adding to the confusion, and an additional prompt to dismiss the dialog, before activation is to happen automatically. Ideally the file should just open. That's why we have auto-activation. This is a wall that gets in the way of seamlessly working."

I agree that this is getting confusing and this is being looked into, so that confusion is not present here.

"I want it to not try to go through Typekit. Not at all. Ever. We don't use it. We've already paid for licensing thousands of fonts from houses that are not Adobe. We want our designers to use those."

Let me get this thing clear when you open a document, InDesign first searches for the fonts in the document on the system if that fails, third party plugins like FEX and Suitcase do the auto-activation to activate fonts (this is failing for you currently), now suppose even these third party plugins are not able to activate some fonts due to any reason (font not being present) then you are thrown this missing fonts dialog which tries to find the fonts on Typekit. So this is the last resort of finding the fonts that can clear the problem of missing fonts.

"What you've done is the equivalent of a shareware ad banner, prompting us to upgrade to the "paid" version to get rid of the ads. Only this is the paid version. You want to advertise your new product to me, find other methods than getting in the way of my work."

Agreed, this is a problem and as already mentioned is something we are actively trying to address.

In short there are 2 problems here,

1. The auto-activation feature of third party applications which is not working currently for you, many people have mentioned on the threads above also that its working for them and for me also it is working fine. I would request you to help us find the cause of this issue that you are facing because we are unable to face this problem at our end.

2. The second issue is the messaging on the Missing Fonts\Typekit dialog that is causing confusion and it automatically finding fonts on Typekit with the user not having any option to turn this off. This is something that we are aware of and actively looking into.

Thanks for being patient

Javed

Report · Sep 19, 2014

Please can a step by step solution be posted, since an adobe acrobat update yesterday Typekit is interfering, all was working perfectly well until yesterdays update. I am unable to load fonts through Suitcase into InDesign. TypeKit is turned off. Indesign is not loading the fonts and is prompting Typekit to open wasting a lot of deadline driven time.