Home > Fonts > Font reporting

Font reporting

Fonts Procedures and Workflows

Last modified: January 14, 2025

Print this page

From 1st January 2025 onward, all new projects involving a print or ebook component need to have a full and complete font report generated for both cover and insides, and these need to be submitted via an Asana form to a Google Drive location in that form.

Purpose

To fulfil compliance responsibilities of the new agreement with Monotype, DK needs to report back all print and ebook use of fonts (those supplied through Monotype Fonts library) in new projects to Monotype on a quarterly basis.

Current Process

DK UK
Using Fuse > SourceReport > Font Report, generate an interior and cover font report for all ebook projects and send to digitalrights@uk.dk.com

DK Verlag
Internal Font reporting.

DK Alpha
Using Fuse > SourceReport > Font Report, generate an interior and cover font report for all ebook projects and send to digitalrights@uk.dk.com

DK Spain
Internal/External users using Fuse > SourceReport > Font Report, generate an interior and cover font report for all ebook projects and send to digitalrights@uk.dk.com

DK Other
Various

New Process

DK UK, Verlag, Alpha, Spain, Other

  1. Replacing the process above, use Fuse > SourceReport > Font Report to generate a separate cover/interior font report in the XML format for all frontlist projects (print and ebook), including all fonts used.
  2. If unsure of the ebook component, report anyway and we will check.
  3. Submit the two reports into a Google Drive location listed in From 1st January 2025, use the correct submission process: Submit the two XML font reports to the Drive location to this Asana form within two days of the FAP date.
  4. If combined, it is okay to submit one combined report using options in the form.

FAQ


Q: Why is this Process changing?

  • This change reflects updated responsibilities and compliance requirements under our new agreement with Monotype. Consolidating print and ebook font usage ensures transparency and alignment across all frontlist projects.
  • This new process does not affect projects created prior to 1st January 2025 unless there is a significant level of changes made to the project or fonts are used to add material to that project. Email fonts@uk.dk.com if unsure.

Q: What is our new agreement with Monotype?

  • This agreement outlines the terms for DK to license Monotype fonts and utilise Monotype’s platform.

Q: What are the benefits of the new Monotype deal?

  • The updated agreement provides access to a significantly larger font library, with over 200,000 fonts available in the near future.
  • It allows for unlimited users across all DK teams, simplifying access management and removing collaboration bottlenecks.
  • Shared production font status ensures better coordination and cost efficiencies across all of PRH.

Q: What is a Production Font?

  • A Production Font is any font used in the creation of a finished product, including: Books (print or ebook), digital formats (e.g., websites, apps, and digital marketing where the font is embedded).
  • Flattened outputs e.g. image formats, are considered to be created under the desktop EULA and do not need to be included in production font reporting.
  • The fonts used in ebooks remain Production Fonts for as long as the ebook is on sale.

Q: Why is it important to report both cover and interior fonts?

  • Reporting ensures we follow licensing agreements and we don’t miss fonts used in any part of our printed books or ebooks.
  • While DK separates these in a production sense, Monotype regards all font usage the same.

Q: When do I need to report this?

  • Within 2 days of FAP date. This is an expansion of the process of assessing usage rights at FAP+2 and will also cover the ebook use component previously required separately.

Q: Is there a limit to how many production fonts we can use?

  • Yes. The agreement allows for 30,000 production fonts for the entire group, and additional fonts can be purchased in increments of 5,000.

Q: Can I supply PDF co-ed guides for reporting?

  • No. PDF co-ed guides are human readable but unlike XML they are not readily processable for batch reporting at the end of the quarter.

Q: Is this the reporting process we will use moving forward?

  • We are constantly reviewing our processes and will look for faster and more efficient ways to complete this reporting process.
  • We will review and learn from this first reporting period (Jan-Mar 2025).

Q: Does this replace the Digital Rights process?

No. Please continue to supply file locations and assets to the other Digital Rights assessment stakeholders.

Q: Do we need to report on custom/special?

  • Yes. Unlike DK, Monotype does not distinguish between custom/special and frontlist. Even if small additions are made to existing material, we will need to report the fonts used for that new component but not for the existing material.

Q: What’s the difference between a “Production Font” and a “typeface family”?

  • A Production Font is an individual font file (like “Helvetica Bold”), while a typeface family includes all the different weights and styles (e.g., regular, italic, bold) of that font.

Q: What happens if a project or font isn’t reported?

  • Usage is tracked and unreported fonts will be classified as Production Fonts regardless, leading to overreporting and increased costs. It can also lead to these fonts being considered unlicensed. If you feel something may have been missed, flag this to fonts@uk.dk.com

Q: What constitutes a minor correction?

  • As very subjective, Monotype has not defined this in our agreement. Please email fonts@uk.dk.com if unsure.

Q: Can this process be automated?

  • We will work with teams to explore tools or systems to streamline font tracking. For now, manual reports must be submitted as per the new process.

Q: Does DK have to report other types of font usage?

  • Yes. We will also need to report web and app use but we will manage these responsibilities through DK Technology.

Q: Who can I contact for help?

Action Required

  1. Update Your Process: Begin reporting all font usage in print and ebook projects (frontlist and special/custom) from 1st January 2025, including all fonts used for covers and interiors.
  2. From 1st January 2025, use the correct submission process: Submit the two XML font reports to the Drive location to this Asana form within two days of the FAP date. This will allow DK to manage and automate as much of this reporting as possible.