Server-based Font Management Best Practices


Published on

Understanding your organization's responsibility to accurately license all of the fonts used in your workflow is just the first step in the process of managing your fonts. In this presentation, Jim Kidwell shows you how to accurately asess your organization's font library and workflow so that you can keep your team creatively charged, efficient and safe from lawsuits.

Published in: Design, Technology, Art & Photos
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Server-based Font Management Best Practices

  1. 1. Server-based Font Management Best Practices<br />Jim Kidwell<br />Extensis Product Marketing Manager<br />
  2. 2. Who am I?<br />Extensis Product Marketing Manager<br />With Extensis for the past 8 years<br />Writer, Speaker, Font Fanatic<br />
  3. 3. Agenda<br />Why server-based font management?<br />Why font compliance?<br />Assessing your needs<br />Locating resources<br />Defining a workflow<br />Implementing a solution<br />Define ongoing assessment<br />Q & A<br />
  4. 4. Why Server-based Font Management?<br />
  5. 5. Checklist<br /><ul><li>Do you have multiple users that work together on projects?
  6. 6. Does your team struggle to keep font libraries in sync?
  7. 7. Are you ‘less than confident’ that your font library is properly licensed?
  8. 8. Do you get helpdesk calls related to font issues?
  9. 9. Does your business lose money if the wrong font is used in production?
  10. 10. Are you accountable to a client if the wrong or improperly licensed font is used?</li></li></ul><li>Benefits of Server-based Font Management<br />Font synchronization<br />Reliable storage and distribution<br />Font compliance management<br />
  11. 11. Why Font Compliance?<br />
  12. 12. Rick Santorum’s agency RaiseDigital sued by Typotheque<br />“…seeking at least $2 million in damages…”<br />…“unauthorized derivative version”…<br />
  13. 13. Wizarding World of Harry Potter sued by P22 Type Foundry <br />“P22 seeks actual or statutory damages of at least $1.5 million as well as the destruction of all merchandise created with the Cezanne software.”<br />
  14. 14. Hadopi (French anti-piracy group) embarrassment<br />
  15. 15. NBC sued by Font Bureau <br />“…suing for $2 million…”<br />“…fonts may be protected by copyright so long as the font qualifies as computer software or a program…”<br />
  16. 16. Red Hat sued by Monotype<br />Settled for $500K<br />
  17. 17. Needs Assessment<br />Font users<br />Hardware & software<br />
  18. 18. Locate Font Resources<br />Original source is best<br />Collect from user machines/servers<br />FontDoctor to collect<br />Font Management Best Practices Guides<br />
  19. 19. Begin License Assessment Process<br />Original EULA with purchase<br />Purchase Orders<br />Fonts that are licensed with other products<br />Operating System<br />Design Software<br />Don’t Stress! This can be an ongoing process<br />
  20. 20. Analyze how documents move throughyour organization<br />
  21. 21. Workgroups<br />By need – editorial, production, design, administration<br />By publication<br />By client<br />Special users will become apparent by workgroup type<br />
  22. 22. Font Acquisition Process<br />Trial purchases<br />Preview-only workgroups<br />IT acquisition<br />
  23. 23. Implement a Solution<br />Setup hardware<br />Install server<br />Add fonts, setup workgroups<br />Connect to Active Directory/Open Directory, add users<br />Configure automatic backups<br />Rollout client software<br />TRAIN your users<br />
  24. 24. Periodic Inspection<br />What to track? <br />Set a schedule<br />Run reports to ensure compliance<br />
  25. 25. Resources + Q & A<br />Font Management Best Practices Guides<br />Server-based Font Management <br />Font Management in Mac OS X<br />Universal Type Server<br />