Upstream software project

eot-utils

Create or examine EOT font format files

About eot-utils

Create or examine EOT font format files

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.eot-utils: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
eot-utils
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
W3C
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The eot-utils are the two programs mkeot and eotinfo. The former creates an EOT (Embedded OpenType) file from an OpenType or TrueType font and the URLs of one or more Web pages, respecting the TrueType embedding bits. The eotinfo program displays EOT metadata in a human-readable way.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package eot-utils

    43 (Fedora 43) (Unspecified): Create or examine EOT font format files

    1.1-47.fc43: aarch64 x86_64

    Source: eot-utils

Fedora 44

  1. Package eot-utils

    44 (Fedora 44) (Unspecified): Create or examine EOT font format files

    1.1-48.fc44: aarch64 x86_64

    Source: eot-utils

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.