Skip navigation
Currently Being Moderated

Missing/Hidden fonts after creating a package

Apr 9, 2012 1:10 PM

Tags: #cs5 #fonts #indesign #indesign_cs5 #missing_fonts #packaging_problem



Our graphics department connects to a Lion server with Font Explorer so all the fonts are centrally located. When creating a package in indesign they can see the selected fonts but after the package has been created the fonts that are on the server are missing/hidden in the package and the fonts that remain are ones that are installed locally on the iMac's. Any idea what would be causing this?

  • Currently Being Moderated
    Apr 11, 2012 11:43 AM   in reply to sdumire

    What version of ID are you using?

    Mark as:
  • Currently Being Moderated
    Apr 16, 2012 6:13 AM   in reply to sdumire

    Hey sdumire - thanks for posting here. My colleague and I ran into this exact same bug with FontExplorer only today, and you've saved us a lot of time troubleshooting.


    The following is the temporary solution we're using until Linotype actually resolves it:


    1. Create a folder on the desktop called Packaged


    2. Create a shell script called with the following contents:


         #! /bin/sh

         # This script 'unhides' packaged fonts hidden by Linotype FontExplorer Pro

         chflags -R nohidden ~/Desktop/Packaged/


    3. Drop this shell script into the local script folder for an affected Studio operator - ie ~/Library/Scripts


    4. Launch Automator, create a new Folder Action called UnhidePackagedFonts and set the Folder Action receives files and folders option to the Packages folder you created on the desktop in Step 1.


    5. Add a Run Shell Script step per the Automator screenshot below, entering the path to the shell script you created in Step 2:



    6. Save the Folder Action, and quit Automator.


    Now when the studio operator packages a job, she can just export it to the Packages folder you created on the desktop. The previously hidden fonts will automatically 'appear' after a few seconds.


    Whilst this workaround does involve a few (very, very easy) steps, it has the advantage of not requiring the operator to manually drop the package onto a script after each package export from InDesign.

    Mark as:
  • Currently Being Moderated
    May 24, 2012 8:07 AM   in reply to Worst-screen-name-ever

    No need for a folder action, using the tips from the link below. You can use the script directly in the automator… and save it as a service. Simply right click on a file or folder and run the service.


    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points