No warning is given, and unless the operator checks Font Usage immediately, the file is permanently changed when it is saved. So if Operator A used Postscript Type 1 Helvetica Bold Italic (plain), when Operator B opens the job, the FILE is now changed to use Helvetica.dfont (bold, italic). Suitcase will then load any available version of a font with the same name.
Operator B then opens the job, but the correct fonts are not available to Suitcase on their Mac. Operator A works on a job, using fonts available to Suitcase on their machine. (I saved the worst for last) More than one operator will work on the same job. When the job is "collected for output" either through the application or Flightcheck, it does not collect symbol even though it is loaded.ģ. Suitcase does not automatically activate the font. The character is often on a text-heavy page, and the operators don't notice it is missing. The font usage does not show symbol as being used. The application does not alert you that the symbol font is not loaded. The obvious solution is to load the symbol font, except that opens the door to operator error: If we don't activate Symbol, the character drops out and we get a blank space. The applications see the character as being in the same font as the rest of the paragraph (universe, futura, etc.) but in reality it is coming out of the symbol font. We pick up old jobs that use characters like the "greater than or equal to" or "plus or minus" math symbols. The most obvious: we have multiple versions of the same fonts on our server, and the wrong font opens and we get reflow.Ģ. Operators created job-specific sets and activated fonts as needed.ġ. In my previous 2 companies, we used Font Reserve with Auto-Activation off. This is a new position for me, and this company has been having a lot of font problems that I haven't encountered in quite a while. Suitcase Fusion 12.1.6 Using Auto Activation and Font Sense
0 kommentar(er)
