# Libron font build, variants, and e-reader use > Libron is a manually revised version of Readerly for digital books, with desktop, KOReader, Kobo, CrossPoint Reader, and webfont builds. Its source is available, but its Reserved Font Name condition means that modified distributions cannot keep the Libron name. **nicoverbruggen/libron** — A manually tuned font revision of Readerly, with reduced and altered serifs, optimized for digital reading and e-readers. OFL licensed. - Repository: https://github.com/nicoverbruggen/libron - Website: https://nicoverbruggen.be/fonts - Stars: 1,948 · Forks: 22 - Language: Python - License: NOASSERTION - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/nicoverbruggen-libron ## Why Libron revises Readerly for long-form digital reading Libron addresses a specific typography problem in ebooks: familiar reading fonts can become visually loud on an e-reader screen. The project began as an attempt to make Readerly more suitable for reading books, particularly after expressive serifs and capital forms drew attention during use. Rather than creating an unrelated typeface, it retains Readerly's proportions and general character while reducing some of those distracting details. The repository describes Libron as a successor to Readerly. Readerly itself is based on Newsreader, so Libron belongs to an existing type design lineage rather than presenting itself as a standalone invention. That relationship matters for adoption decisions. Users who already prefer Readerly may see Libron as a controlled revision, while users seeking a substantially different voice may find the resemblance between the two fonts limiting. The target audience is therefore narrower than that of a general-purpose font collection. Libron is aimed at people reading books on desktop or e-reader devices, especially KOReader and Kobo users who can select the corresponding build. It can also serve web publications through its WOFF2 variant and CrossPoint Reader through a dedicated `cpfont` package. The documentation does not claim suitability for interfaces, signage, display typography, or other applications outside book reading. The design work includes redrawn or refined uppercase and lowercase letters, figures, and punctuation across four styles. Spacing and kerning were adjusted with the outlines, rather than treating those metrics as a later concern. Accented characters were rebuilt where necessary to remain consistent with their corresponding base glyphs. Libron also adds synthetic small caps made from scaled capitals for each style. These changes give the project a coherent editorial focus, but they do not erase its origins as a manual revision of an existing font. ## Libron's FontForge source and four-style rebuild process The repository stores editable source files in `src`. According to the README, the original font was imported and then manually edited with FontForge. This means the distributed binaries are not the only representation of the project. A developer can inspect or change the outlines in those source files, but the workflow also depends on the repository's build scripts and font tooling. Tagged commits trigger an automatic release. During that process, the value in `VERSION` becomes the font version and is embedded in the resulting fonts. The project therefore has a visible version marker and automated publication path, although the README does not document the individual commands used by the hosted release workflow. The build produces several targets because e-reader software does not all consume the same packaging and spacing conventions. The standard desktop output uses `TTF`. Libron R targets KOReader with relaxed line spacing, also as `TTF`. KF Libron targets Kobo devices and uses the `KF TTF` format associated with the referenced Kobo font fix. CrossPoint Reader receives a `cpfont`, while the webfont target uses `WOFF2`. Those variants are a practical reason to review the packaging rather than treating every Libron download as interchangeable. In particular, the KOReader and desktop builds intentionally differ in line spacing, and the Kobo build is not described as an ordinary TTF distribution. The README does not document every style name, font-family setting, or device installation path, so it would be unsafe to infer them. ## Building Libron locally with Podman, Docker, or Python The preferred local build command is `local-build.sh`. The wrapper selects Podman when available and falls back to Docker when Podman is not installed. Before running it, install either container runtime because the project documentation requires one. Use the help option to inspect the supported choices and where the wrapper places its output rather than guessing those paths. ```bash ./local-build.sh --help ``` This displays the script's options and output locations. The README does not reproduce that help output, so the exact list of flags and directories must be confirmed on the local system. When all dependencies are already available, the repository also offers `build.py` directly: ```bash ./build.py ``` This is the local Python entry point for building the font, but it is not presented as a dependency-free command. The README does not specify the Python version, package installation command, or dependency manifest. For a first reproducible build, the wrapper is the documented choice because it encapsulates the build environment in Podman or Docker. There is no installation tutorial for placing fonts into a reader. The README explains what is generated, but it does not give exact menu paths for KOReader, Kobo, or CrossPoint Reader. It also does not publish a direct download command. A sensible first use is to obtain a released variant from the project's releases, verify that it matches the target reader, and inspect its metadata or specimen in that reader with a page containing accents, figures, punctuation, italics, and small caps. The repository includes `specimen.svg` and `sample.svg` as visual references. ## Choosing the correct Libron package for an e-reader Package selection is one of the clearest adoption constraints. Choose the standard `TTF` build for desktop reading. Choose Libron R when the reader is KOReader and relaxed line spacing is wanted. Choose KF Libron for a Kobo device, using the project's stated `KF TTF` output rather than substituting the desktop build without evidence that it works. The choice changes more than file extension. The KOReader variant is deliberately built for different line spacing, so the same outlines can produce a different page texture depending on the package. The Kobo target is tied to a specific device-oriented format. For CrossPoint Reader, use the generated `cpfont`. A browser or web publishing workflow can use the `WOFF2` target. Users should not infer installation details from these package names alone. The README does not explain how to transfer files, whether existing fonts must be removed, whether a restart is required, or whether every device accepts the same style set. Those checks belong in the device-specific documentation rather than this repository. The safe point is to select the documented target and confirm the resulting files before replacing an existing font. The four styles and synthetic small caps make it worth checking more than plain lowercase text. Italics, punctuation, figures, accented characters, and small caps are areas where editorial fonts reveal inconsistencies. The repository's specimen and reading sample are useful for visual comparison, but a sample cannot substitute for testing a book page on the target display. ## Libron's build limitations and manual-design trade-offs Libron is not a general build tool. The repository contains font-specific Python and shell entry points, editable FontForge sources, and a small set of packaging targets. Its scripts should not be treated as reusable automation for arbitrary font families without reading their contents and dependencies. The README does not document supported FontForge versions, operating systems beyond the available container runtimes, Python versions, or failure recovery procedures. Manual editing also affects change management. Because source outlines have been adjusted alongside spacing and kerning, an outline change can require judgment about related glyphs and metrics. Accent rebuilding and synthetic small caps are examples of features that depend on design consistency rather than a purely mechanical export. Automated tagging helps package releases, but it does not remove the need to decide which changes belong in all styles and which apply only to a particular device variant. The README also leaves compatibility questions open. It does not list supported e-reader firmware versions, font caches, install permissions, or validation results for Kindle despite Kindle appearing as a repository topic. Therefore, this documentation supports choosing the named KOReader, Kobo, CrossPoint Reader, desktop, and web targets, but it does not establish compatibility for every Kindle model or every ebook application. A related limitation is visual neutrality. Libron deliberately keeps Readerly's proportions and overall character. Readers who wanted the stronger serifs or capitals removed rather than restrained may find that the revision has not gone far enough. Readers who dislike Newsreader's underlying proportions may still dislike Libron. ## Licensing, versioning, and ongoing maintenance cost The README identifies the font as available under the OFL license and describes Libron as a Reserved Font Name. Modified versions must use a different primary font name unless Nico Verbruggen gives written permission. That restriction affects fork naming, embedded font metadata, and how a distributor presents a derivative, regardless of the broader permissions associated with the OFL. This is a font project, so the repository being labeled primarily as Python does not imply that adopting it means adding a conventional Python dependency to an application. Most adoption work concerns downloading a generated font, choosing the correct package, and confirming device compatibility. Maintainers who fork the outlines incur a design and release burden instead: source edits, version metadata, generated assets, device formats, and Reserved Font Name compliance must all be managed. The project is not archived. Its last push was on 2026-10-16. Recent releases include `v0.31` on 2026-10-09, `v0.30` on 2026-10-06, and `v0.25` on 2026-09-05. The version in `VERSION` controls the version embedded in automated font builds, which provides a concrete identity for generated binaries. The documentation does not describe a long-term support policy or a separate compatibility matrix. For an evaluator, the key distinction is between using released binaries and maintaining a fork. Binary use has a low technical adoption cost but still requires selecting the correct reader variant. Forking has higher maintenance cost because the project relies on manual FontForge edits, multiple generated formats, and a naming restriction. The repository's `CHANGELOG.md` and `LICENSE` are the relevant files for checking release-specific changes and exact licensing terms. ## Libron compared with installing stock Readerly or Newsreader Libron differs from stock Readerly through cumulative outline, spacing, kerning, accent, and small-cap revisions rather than through a different font pipeline. Readerly is its direct design base, and Newsreader is the underlying font identified farther back in that lineage. Libron is appropriate when a reader wants Readerly's proportions with quieter details and a more neutral editorial appearance. If preserving the original Readerly or Newsreader design is the goal, installing the upstream font is the more direct choice. Libron adds manual revision work and device-specific outputs, so it should not be selected merely because it is newer or because its repository offers several packages. The practical distinction is visual: Libron reduces and alters serifs, refines capitals and other glyphs, and adds synthetic small caps while retaining the source design's character. For readers with an established font workflow, another static reading font may offer broader device documentation or more predictable package behavior. The repository does not compare Libron with named alternatives or publish device test results, so the project-specific decision should follow from whether its revised shapes and target-specific spacing fit the reader's preferred typography. ## Conclusion Readers who want a quieter, neutral serif based on Readerly should first try the appropriate released Libron variant on a representative book page. Developers should inspect build.py and local-build.sh before adopting it as a build dependency, while distributors of modified fonts must choose a different primary font name unless Nico Verbruggen provides written permission. ## FAQ ### What is Libron, and which font is it based on? Libron is a manually edited font revision of Readerly intended for digital reading and e-readers. Readerly is based on Newsreader, and Libron retains Readerly's proportions while revising serifs, capitals, spacing, kerning, accented characters, and small caps. ### Which Libron file should I use for KOReader or a Kobo? The README identifies Libron R as the KOReader variant, with relaxed line spacing. For Kobo devices, it identifies KF Libron as the `KF TTF` build. ### Can I build Libron locally with Python? Yes, but the README says the dependencies must already be installed locally. The documented commands are `./build.py` for a local build and `./local-build.sh` for a containerized build using Podman or Docker. ### Can a modified Libron font keep the Libron name? The README says Libron is a Reserved Font Name. Modified versions must use a different primary font name unless Nico Verbruggen gives written permission. ## Sources - [Issues](https://github.com/nicoverbruggen/libron/issues) - [nicoverbruggen/libron on GitHub](https://github.com/nicoverbruggen/libron) - [Project website](https://nicoverbruggen.be/fonts) - [README](https://github.com/nicoverbruggen/libron/blob/main/README.md) - [Releases](https://github.com/nicoverbruggen/libron/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/nicoverbruggen-libron