Fonts can cause issues when creating developing and outputting documents in the publishing workflow. See what types of things are required for you and your team to flawlessly use fonts in your workflow.

1. PUBLISHING AND FONTS
WHAT’S THE ISSUE?
Presented by Jim Kidwell

2. Agenda

3. Publishing Font Issues
• Evolving team structures
• Distribution issues
• Compliance
• Creative disconnect
• Process output automation

4. Evolving team structures
• More connected professionals
• Geographic challenges
• Varying team member needs
! IT
! Creative
! Editorial
! Production

5. More Fonts, More Problems
• Years of purchases
• Large font collections

6. Many Digital Font Formats
• Bitmapped
• PostScript
• TrueType
• TTC, Multiple Master, dfont, AAT, etc.
• OpenType

7. Font Distribution &
Synchronization

8. Distribution &
Synchronization Solves
1. Solve technical issues
a. Missing fonts
b. Incorrect fonts
2. Brand control
3. Font compliance

9. Workgroup Distribution

10. By User Type
Production
Design
Editorial

11. By Client
Ford
Macy’s
Nike

12. By Project
Website
Collateral
Event

13. Compliance

14. Font Licenses
• Typeface designs cannot be copyrighted
• Fonts are licensed as software

15. Compliance Strategies

16. Compliance through
workgroup access

17. Compliance through
user permissions

18. Compliance
for all users

19. Creative Disconnect
• Want creative exploration & inspiration
• Don’t know what the team has
• “Close enough” isn’t good enough
• Everyone has the “me toos”

20. What Solutions
Do Creatives Need?

21. A Font Dashboard

22. Ability to Search

23. Find Similarities - QuickMatch

24. Preview fonts

25. Detailed Data

26. Plug-in based font activation
• Adobe Creative Cloud
! InDesign
! Illustrator
! Photoshop
! InCopy
• QuarkXPress

27. Every Font At Hand

28. A Little Fontspiration

29. Process output automation

30. Resources
Font Management Best Practices Guides
• Server-based, OS X and Windows
• www.extensis.com/fmbpg
Universal Type Server
• www.typeserver.com
• Free 30-day trial
Connect
• @extensis
• @jimkidwell