OSX El Capitan - Issues, fonts, yada yada yada

Out of context: Reply #11

  • Started
  • Last post
  • 21 Responses
  • oey0

    Okay, or not okay...

    FontExplorer has the deactivate option when quitting the Program.
    But even with that option not checked...what happens is that when I shut down the computer, or restart, all activated fonts will be deactivated.

    When I close the program and open it during a session without logging out fonts are still activated.

    I don't have FontBook installed in case you're wondering.

    I'm considering in buying FontExplorer's latest version though I'm not doing any professional work right now but I have doubts if the problem will persist or not...

    I'm right now redesigning my website and selcting work for a fresh portfolio and would like to work on some stuff to print it and make some photos of my work but it's a pain in the ass to have to activate all the fonts all the time or to make a folder for each project now.

    The computer already came with El Capitan installed...

    • You should have font book installed. It's system software and I'm not sure it's easily removed without serious issues.monospaced
    • i always read you shouldn't have them both installed because of conflicts. and also i have uninstalled system software since my first mac without problems.oey
    • but thanks for your advice mono!
      seriously.
      oey
    • You shouldn't have both Font Book and FontExplorer X (or any other font manager) *running* at the same time. FontExplorer X warns if this is the case.evilpeacock
    • And you should update to the latest FontExplorer when dealing with new operating systems. 5.5 just released with mostly bug fixes and improved OS support.evilpeacock
    • I don't have both installed, only FontExplorer X. Yes, I should update it but I was trying to save some money since I'm not doing any professional work now.oey
    • I know what you mean and I fully agree.oey
    • I'm having the same issues with FontEx even though I'm not in elCap. known issues. I have found a few fixes that work for a while - I'll dig them upGnash

View thread