Managing fonts in Collabora Online

Use a fixed reference set built from your organization's own documents, kept under version control and reused for every update. Include at least one file for each format your users open, such as docx, xlsx, pptx, odt and PDF, and make sure each file uses the corporate fonts and the fallback fonts your users actually see. Store the originals with a short note on which fonts each file depends on, so a failed check can be traced to a specific font rather than a vague sense that something looks different. Your own documents will surface problems that a generic sample set misses, because they reflect your templates, your tables and your font choices.

Run the same reference set through a staging instance on the current version and again on the target version, then compare the outputs side by side. Staging should match production in font configuration, WOPI host settings and the Collabora Online package or image tag, so differences come from the update itself. Export each document to PDF on both versions and compare the pages visually, looking for substituted glyphs, shifted text and changed spacing. Keep the rendered PDFs with the update record so the comparison can be repeated or reviewed later by your team or an auditor.

Check that the fonts are still installed in the systemplate and that the remote font configuration still points to the right source after the upgrade. For package installs, confirm the font files and any font configuration in the Collabora Online configuration are unchanged, and for Docker or Kubernetes deployments, confirm the image tag and any mounted font volumes or configuration maps still apply. Open a reference document and check that the fonts reported in the document match the ones you installed. Treat a missing font as a failed check even when the document still opens, because the layout will look correct until a line break or table width changes.

Check the features most sensitive to font metrics: line breaks, pagination, table widths and text fit. In Writer, look at where page breaks fall, whether headers and footers stay aligned, and whether long paragraphs wrap at the same points. In Calc, check column widths, cell text overflow, number formatting and printed page breaks. In Impress, check text boxes for overflow, title placement and whether text stays inside placeholders. Compare each check against the staging baseline rather than against your memory of how the document should look, because small differences are easy to miss when reviewed by eye.

Record the font names the document reports for each reference file, both before and after the update. Compare the list against the fonts you expect, noting any name that has changed, any name that is missing and any substitution that appears where a corporate font should be used. A stable record makes it possible to spot a substitution introduced by an update even when the rendered page looks close enough at a glance. Keep the list with the reference set so that the next update compares against a known baseline, not against whatever the previous version happened to show.

Agree the rollback steps before the update starts, and name who can decide to roll back and within what window. Keep the previous package version, image tag or configuration backup available so the earlier state can be restored without rebuilding the server. Define the failed checks that trigger a rollback, such as a missing corporate font or broken pagination in a document your users rely on, and decide whether a known substitution can be accepted for a limited period. Confirm the rollback steps in staging first, and record the decision and the reason in the change record so the outcome is traceable.

The effort depends on how many corporate typefaces you must support, how long the licensing review takes, how many Collabora Online servers need the same fonts, and how often you update. A small set of licensed fonts on one server is a contained task. Each additional typeface adds files to package, test and track, and each additional server adds a place where fonts can drift apart. Ask any partner to split the quote into a one-time setup (font inventory, licensing review, initial installation and rendering tests) and a recurring part (re-checking fonts after each Collabora Online update and adding new faces). Make sure the quote states which of those items it covers.

Yes, if you have a named engineer who can install font packages on the Collabora Online host, edit the systemplate, and compare rendered output against a reference set of documents. The work becomes harder when fonts must be licensed for a server environment, when several servers must match exactly, or when the same person is not available for each update. Collabora Online is licensed under MPL-2.0, but that license covers the server code and does not decide whether you may install a given commercial typeface on your servers, so the licensing review belongs to your legal or procurement team in either case.

Prepare four things before any work begins. First, the font files you intend to use, with the license terms for each typeface and proof that you hold the right to install them on servers. Second, a set of sample documents that represent how your staff work, including the Microsoft Office files and PDFs that currently look wrong or differently spaced. Third, a staging instance of Collabora Online that matches production as closely as you can make it. Fourth, a named owner on your side who can approve licensing decisions and sign off on rendering results. Without the owner, decisions about which font substitutes are acceptable will stall the project.

No. The sample fontserver from the CollaboraOnline project serves TrueType and OpenType fonts for the remote font configuration feature, and its own documentation states that it is intended for development and testing, not production. Use it to prove that remote fonts load and render as expected in a lab. For production, plan a font delivery path that you control, with HTTPS in front of it, access limited to your Collabora Online servers, and versioned font files that match your licensing records. Check the fontserver README before you start, because its scope may change between releases.

Treat font checks as a required step in every update, not an optional extra. Collabora publishes point releases on its branches, and the 25.04 release notes show that the branch kept receiving point releases well after its first release, so updates will be frequent. Before you roll a new version to production, render your reference documents on staging, compare pages, tables and line breaks against the approved output, and confirm that the remote font configuration still loads. Keep a record of each result so that an unexpected change can be traced to either a Collabora Online update or a font change.

Differences usually appear where a document uses a font that is missing on the server, so LibreOffice falls back to a substitute with different metrics. Corporate typefaces, custom Office fonts and older Windows fonts are the usual causes. Metric differences move line breaks, page breaks and table widths, which matters most in contracts, forms and regulated reports. Ask your team to list the fonts found in the documents that matter most, then confirm which of them are installed, licensed and tested. Fonts that appear in only a few legacy files can often be handled with a documented substitute if the business owner accepts it.