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 · Jun 24, 2016

i also got more and more font problems with adobe products. i also would like to get rid of typekit, but i guess its not possible because adobe said so i cannot say where exactly the problem is, but it feels like there are some conflicts between adobe cc and fontxplorer. there are many fonts which worked fine until one day, indesign, or illustrator cannot find them anymore and in font explorer they just disappeared/cannot be loadet anymore. of course adobe will claim that its a problem from fontxplorer and the other way round. any help pls?

Report · Jan 12, 2016

I was happily using a font in a PS document. Without warning the program told me that the font, for which I have bought a perpetual license, was no longer available. I uninstalled the font and reinstalled it.

When I started using PS in the early 90s I was grateful to the software designers.

I beta tested Stonehenge (CS5 extended) and was grateful to the Stonehenge team.

Today that gratitude has soured and it is thanks to Typekit.

Typekit is becoming a deal breaker. Typekit is strangling my workflow.

Perhaps I will throw in the towel and move to OnOne, Quark and Corel.

In this sense it is a good thing that the licensing is month-to-month.

(broken hearted)

J

Report · Feb 08, 2014

@Quesinberry, I feel your frustration entirely!

Typically we attempt to work out any technical issues from within our studio ourselves. In the past I've always assumed that the glitches have been our errors, or at least user errors at this end - to the annoyance of our team members I'm sure. Now though, after dealing with CC for the past few months, I've re-assessed this position and am now resigned to the fact that the Adobe software is more than often the actual problem... and we're the guinea pigs dealing with the fallout. You're definitely not alone in being jaded with the current state of affairs here, and you're definitely not alone in the amount of time you are spending on this.

I'm sure some people out there do not care, and find other work-arounds, however I feel like we invest a decent amount of money in these business tools that Adobe supplies to us, and therefore we'e entitled to receive a product that actually works well in a real world environment - not only in a world where Adobe is the only software company we use.

We understand there are a large set of variables to deal with (we have software developers at work) however, at this stage, I don't know why we're unable to choose to simply remove, or turn off, the offending piece of software? We don't use it, we don't really want to use it as yet, and even if we choose to use it down the track we will not do so until we can work out the cost benifit of modifying our workflow to include it (and at this stage it'd need to be a whole lot better).

... ok, Ben@Typekit Support, we're looking forward to you putting a smile on our faces now 😉 thanks.

Report · Jun 24, 2014

Thanks for this conversation y'all... helped out a lot!

Just had the same problem after updating to CC 2014.. FontExplorer need to time updates to plugins with Adobe as I think this is also part of the problem!

That said, I couldn't live without either!

Cheers!

Report · Jun 24, 2014

FontExplorer need to time updates to plugins with Adobe as I think this is also part of the problem!

There is clearly a sizeable body of Adobe customers who use a third party font manager, and rely on it in their day-to-day workflow.

I don't know enough about when and how APIs are published (either at Adobe, or in the industry more generally), but if it doesn't happen already it would be great if Adobe could work with the teams behind Suitcase, FontExplorer, etc and try to minimise the interruptions to the workflow of their mutual customers. Did the font manager software companies only find out about CC 2014 when the public did? If it doesn't occur already is there are way that they can be given early access to the APIs?

FontExplorer feels like it is slow to react when Adobe updates its software (but again, I don't pretend to understand the technological complexity). Is there is a font manager which has a better track record of updating its plugins when Adobe updates its applications?

If this is a problem with all font managers then perhaps Adobe should consider whether there are ways that it can improve the situation for its customers. Because regardless of who is at 'fault' it impacts on Adobe users.

Report · Jun 27, 2014

To all who hate TypeKit. I've been advised to leave a message under Action>report abuse>Harassment> of the following nature, i.e TypeKit in InDesign is constantly intended to disturb or upset, and it is characteristically repetitive and disruptive (insert your personalised situation here), and this will no longer become social commentary but an action that they have to immediatly attend too. The more people who report it, faster the resolution.

Report · Jun 27, 2014

Whoever "advised" you to do that was taking nonsense, and we will ignore any reports of that nature. The Report Abuse feature on these forums is for notifying us about posts made on these forums - nothing else. You have an email address for product feedback. Use that.

konmarinis wrote:

To all who hate TypeKit. I've been advised to leave a message under Action>report abuse>Harassment>...

Report · Jan 22, 2015

Hear! Hear! I hate it, too. In MY workflow at least, it's completely useless and I'd love to just be able to turn it off.

Report · Jul 03, 2014

To be very clear, Adobe does work with plug-in developers and provides them with specifications and tools to prepare their plug-ins for new versions of InDesign well before those new versions release. They are also enrolled in and strongly encouraged to participate in our prerelease program.

For a plug-in developer to claim that they didn't know about the new release, have information about the new release, or have access to prerelease builds is at best misleading to our mutual users. In some cases, plug-in developers have other priorities and assume that they can wait until after we release to provide for their compatibility update release. That is quite unfortunate for all involved. Unfortunately, Adobe cannot force a plug-in developer to heed our calls for them to prepare for our releases.

- Dov

- Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)

Report · Jul 03, 2014

For those wishing for a way to turn off Typekit, you should know that there is an update to Creative Cloud desktop app today.

It appears that you can now turn Typekit off. I don't want to do that because I don't want to use the fonts I'm already using:

Report · Jul 03, 2014

Yippee!!!

Report · Jul 06, 2014

This does not turn off typekit.

I wish like hell that it did.

Report · Jul 06, 2014

It turns off Typekit, because choosing Typekit OFF prevents you from downloading Typekit fonts, even accidentally.

Therefore, it is indeed turned off.

Report · Jul 06, 2014

Actually, it does not fully turn off Typekit, only the synchronization aspect of it.

- Dov

- Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)

Report · Nov 06, 2014

This absolutely does not work. Nice try though!

Report · Jul 13, 2014

Dov Isaacs wrote:

To be very clear, Adobe does work with plug-in developers and provides them with specifications and tools to prepare their plug-ins for new versions of InDesign well before those new versions release. They are also enrolled in and strongly encouraged to participate in our prerelease program.

For a plug-in developer to claim that they didn't know about the new release, have information about the new release, or have access to prerelease builds is at best misleading to our mutual users. In some cases, plug-in developers have other priorities and assume that they can wait until after we release to provide for their compatibility update release. That is quite unfortunate for all involved. Unfortunately, Adobe cannot force a plug-in developer to heed our calls for them to prepare for our releases.

- Dov

Thanks Dov.

I'd be interested to hear what the FontExplorerX team make of this statement - it's almost a month after the announcement of CC 2014 and they still haven't released compatible plugins. Their twitter account suggests that CC-compatible plugins will be released this week (but even then that's only in a Public Reply to a user query - no statement that I can see on the website, and not even a general announcement on Twitter)

Report · Jul 03, 2014

Does this mean that older files fonts are not there any more when I open an older file in the new illustrator cc? Big bummer if so do I have to reassign all the fonts on every file I open...

Report · Jul 03, 2014

@greenair,

Wherever did you get the idea that "older files fonts are not there" when you open in Illustrator CC? Or InDesign CC, for that matter (you are in the InDesign forum)?

Nothing is changed. No one is forcing your to pick new fonts. Completely untrue.

Report · Sep 22, 2016

THANK YOU Greenair!!!!

Report · Jul 06, 2014

When opening a document that contains fonts not present on my system CC would prompt me with the below dialog (hit enter and your in):

Now with CC (2014) I get TypeKit Prompt. (after a wait) then Multiple TABS and an enter later I now have the document open.

it is also still present in the Type menu.

Therefore, it is indeed NOT turned off.

Report · Aug 11, 2014

I am running CC and the latest version of Suitcase, and it is still having this problem , even with Typekit turned off in CC app preferences. It is not just FontExplorerX, so the arguments from Steve etc. on this thread saying it's only font explorer people are false. His flippant attempts to insult and bully those reporting bugs and then deny the existence of the problem are unacceptable for a product I pay a monthly service for. I don't know where Steve got his training (if any) on how to handle customer support but insulting paying customers for reporting problems your product introduced is not how it's done.

Perhaps if an actual Adobe employee instead of a community forum MVP answered this thread (beyond covering's Steve's ass while he bullies people) then there would be some meaningful information instead of more insults and unfounded speculation. That would require supporting the customers though beyond telling them to reinstall everything (which doesn't work, I tried it).

To repeat this point again: All of the frustrated people on this thread are not simply making it up, nor is it their own fault or the fault of the 3rd party vendors, considering Adobe has broken support for both of the popular font managers. It's been months of this crap, fix it please.

It's a good thing for Adobe there is no open source alternative to their products yet... but it's not the rocket science they like to pretend it is, and furthermore the overbearing attempts to lock everyone in the Adobe Lifestyle are being seriously sabotaged by the complete lack of responsive support (and jerk off replies like the ones from our friend above).

And Steve, save your fingers with some beak-off reply, since you actually have no information of use or value whatsoever. I can do my own speculating thanks.

Report · Sep 03, 2014

We handle private label packaging. All designed in Illustrator. I have the same issues using CC and Font Fusion 5. I want my auto activation to activate my customer's fonts. These are specific to their artwork and they own the rights to them to be printed this way. I need the Typekit to allow my autoactivation and not interfere.

Report · Sep 03, 2014

Hi,

I apologise that you are still facing issues with the Fusion.

I tried this on my end on Mac 10.9 using Suitcase Fusion 5 and InDesign CC 2014 and it worked fine. The fonts were able to get auto-activated.

Can you elaborate a little more on the workflow that you are performing with Suitcase Fusion 5.

Please let me know if its OK to get in touch with you to further isolate the issue, if so please share your ID with slight mention of the issue that you are facing on sharewithid@adobe.com

Thanks

Javed

Report · Sep 04, 2014

Hi Mohammad,

Thank you for following up. It has been very frustrating. I think we have too many new elements here to isolate this easily.

I am using a late 2013 MacPro 3.7 GHz Quad-Core Intel Xeon E5. We just upgraded to Suitecase Fusion 5 and updated to the Adobe CC 2014.

I believe that the fonts are getting corrupt on our server. I have our IT guy evaluating, but many fonts (not the OTF) show zero kb.

In the end I tried your test with the Indesign and was able to make the auto activation work. Then I tried it with the Illustrator. It worked when the fonts were resident and I knew that they had a size to them.

I do wish that when the type kit comes up and you have the option of finding fonts – it gave you the option of finding somewhere other than your system. Does this mean for everything to work best all fonts should be in the system folder?

Report · Sep 04, 2014

I havent been able to set-up the server for Suitcase fusion.

I assumed that if it were able to Activate fonts from the local system it would be able to do so from the server.

Regarding your OTF files being of size 0kb i have seen this similar issue where some OTF files if are transferred to a windows file system become 0 kb files. Is the server that you guys are using a windows based server?

"I do wish that when the type kit comes up and you have the option of finding fonts – it gave you the option of finding somewhere other than your system. Does this mean for everything to work best all fonts should be in the system folder?"

I dont think so that should be the case, i will get back on this to you with further info once i try this on my end.

Regards

Javed