adobe-mappings-cmap

Overview

adobe-mappings-cmap packages Adobe CMap resources: character-mapping data used to translate character codes to CIDs in CID-keyed font workflows and related tools. In practical terms, this data helps software interpret and render text correctly when a font or document relies on Adobe mapping resources rather than a simple one-to-one Unicode font mapping. Adobe describes these resources as mappings from character codes, such as Unicode, to CIDs, and notes that the project exists to make the public CMap resources available for reuse in open source projects. (adobe.com)

For NiceOS, this package exists so that font, document, and PDF-processing software that expects Adobe CMap data can find it in the distribution without bundling its own copy. The exact consumers in NiceOS should be verified from the package set and reverse dependencies when updating or rebasing this package.

Purpose and typical use cases

Typical uses for this package include:

• providing CMap resources to PDF and font tools that need Adobe character mappings;
• supporting CID-keyed font workflows;
• enabling document conversion or text extraction tools that expect these mapping tables to be installed system-wide.

Typical users include:

• distribution and package maintainers;
• system administrators who manage document-processing stacks;
• developers working on font, PDF, or text-conversion tooling;
• CI/CD maintainers who need a reproducible packaged dependency instead of ad hoc local data files.

If a local workflow depends on a specific CMap name or a specific character collection, NiceOS maintainers should verify that the corresponding upstream resource is still present and named as expected before updating the package.

Upstream project

The upstream CMap resources project is maintained by Adobe and is available as adobe-type-tools/cmap-resources on GitHub. Adobe’s documentation also points to the project as the current home for the public CMap resources and the related technical notes. (github.com)

For background, Adobe’s technical notes explain that CMap resources define mappings from character codes to CIDs, and that these resources are intended for use with CID-keyed fonts and related document workflows. (adobe.com)

Dist-git repository contents

This dist-git repository is organized as follows:

• SPECS/ — RPM spec files and packaging logic.
• SOURCES/ — source manifests and other source-control metadata used by the packaging workflow.
• METADATA/ — repository metadata maintained for the package.
• SBOM/ — software bill of materials material, when present for this package.

The repository is intended to hold packaging metadata, not a full upstream source mirror.

Source storage and integrity policy

Large upstream source archives are intentionally not stored in this Git repository. Instead, the packaging workflow keeps source integrity information in manifest files under SOURCES/. That lets maintainers track what should be fetched and verified without checking bulky upstream archives into dist-git.

When updating the package, NiceOS maintainers should confirm that:

• the manifest entries still match the expected upstream sources;
• the installed CMap names and file layout remain compatible with reverse dependencies;
• any packaging metadata generated from the source set is still correct after the update.

Do not rely on this repository as the authoritative storage for the upstream payload itself.

NiceOS maintenance notes

Before updating this package, check the following:

• upstream project layout and file names used by the package still exist;
• any manifest or source-tracking files in SOURCES/ need regeneration;
• spec logic still installs the expected resource paths and excludes nothing needed at runtime;
• license files and package metadata remain accurate;
• dependent packages that read CMap resources still resolve the same resource names after the update.

Risks to consider:

• a renamed or removed CMap file may break downstream font or PDF tools;
• packaging changes can affect file locations even if the upstream data is unchanged;
• generated packaging metadata may need to be refreshed if the source set changes.

If the upstream project changes its layout or publishing method, NiceOS maintainers should verify the update process before relying on automation.

Build and verification checklist

Use this checklist for RPM maintenance work:

• confirm the upstream source set referenced by SOURCES/ is complete and current;
• review the spec file for install paths, file ownership, and any %files changes;
• rebuild the SRPM and RPMs in a clean environment;
• verify that the installed package contains the expected CMap resources;
• run package QA checks used by NiceOS for file-list, metadata, and policy compliance;
• test at least one known consumer if available in the build environment;
• review the resulting SBOM or metadata artifacts if this repository publishes them;
• check that no unintended source files or generated outputs were added to dist-git.

References

• Adobe CMap Resources & Character Collections
• Adobe CMap and CIDFont Files Specification
• Adobe Font Technical Notes
• adobe-type-tools/cmap-resources

Russian documentation

See README_RU.md for the Russian documentation.

Dist-git repository notes

• Package repository: rpms/adobe-mappings-cmap
• NiceOS branch: niceos-5.2
• This README is intentionally stable and does not include EVR, source archive checksums or lock hashes.