Aabestfontgenerator.
THE TYPE NOTEBOOK

Classico Font: URW’s Zapf Design and the LaTeX Package

Understand Hermann Zapf’s URW Classico, its Optima relationship, and the difference between LaTeX package distribution and commercial font licensing.

This guide covers Hermann Zapf’s URW Classico and the separately documented LaTeX distribution. Identify which resource and terms you are using before treating similarly named packages as interchangeable.

Sources reviewed .

ORIGINAL PUBLISHER SPECIMEN

Explore Classico at the source.

The editable specimens below are independent alternatives. Use the publisher’s preview for the original family.

View the original on URW Classico original publisher specimen ↗
COMPARE REAL FONTS

Compare open-license alternatives.

Read the selection notes ↓

Enter the same words in each specimen to compare. These are editorial starting points; explore each family for its background and license.

LIVE TYPEFACE SPECIMEN

See your words in Marcellus.

Real font preview
Loading Marcellus…
Get font from the official source ↗

This preview uses a real font. Copying ordinary text into another app will not carry this font with it. The PNG keeps the visual appearance.

Explore Marcellus: history, styles and license ↗

LIVE TYPEFACE SPECIMEN

See your words in Jost.

Real font preview
Loading Jost…
Get font from the official source ↗

This preview uses a real font. Copying ordinary text into another app will not carry this font with it. The PNG keeps the visual appearance.

Explore Jost: history, styles and license ↗

01

Separate the typeface identity from its distribution

The CTAN package maintainer’s description identifies URW Classico as Zapf’s revision of Optima for URW. It explains that Artifex made original fonts available for non-commercial distribution, that URW corrected fonts and added accented glyphs, and that the package supplies Type 1 fonts, metrics and LaTeX support. The commercial URW family listing separately credits Zapf. A package’s support-file license is not automatically a blanket commercial license for its font files.

02

Test a complete multilingual document rather than one heading

If you are selecting the LaTeX package, create a proof containing your actual accented names, bibliography entries, numerals, punctuation and emphasized phrases. Inspect the generated document rather than assuming a successful package load proves every required glyph is present. Keep the chosen font resource and its terms in the project notes so collaborators can reproduce the same output. When moving an existing Optima document, compare line endings and pagination: a design relationship does not promise identical metrics.

03

Choose the right source for the intended output

For commercial artwork or web use, review the relevant publisher offering and license instead of carrying a non-commercial package assumption into another project. The Marcellus and Jost profiles here are independently designed comparisons, not Classico font files. Our Unicode lettering converter offers copied character substitutions for simple text destinations; it cannot supply the URW alphabet, LaTeX metrics or font embedding permissions. Use the actual resource when consistent document typography is the task.

GOOD QUESTIONS

Your questions, answered.

Is URW Classico related to Optima?

Yes. The CTAN maintainer describes it as Hermann Zapf’s revision of Optima for URW; that relationship does not make every distribution or its metrics identical.

Does the LaTeX package make every use of Classico commercial-use free?

No. Read the font and support-file terms separately. The package description explicitly discusses non-commercial distribution, while the publisher also offers commercial licensing.

Sources & background

Sources supporting this page’s explanations. Practical examples are our editorial suggestions.