Upstream software project

sugar-read

A document reader for Sugar

About sugar-read

A document reader for Sugar

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.sugar-read: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
sugar-read
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-2.0-or-later
Source repository
Not reported

Source-reported description

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

The Read activity allows the laptop to act as a book reader. It has a simple interface, and will view many kinds of text and image-based book- like materials. It will have particular strengths in handheld mode, with extremely low power consumption and simple navigation controls. Read can read PDF files, single-page TIFF files, and also read DJVU files.

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 sugar-read

    43 (Fedora 43) (Unspecified): A document reader for Sugar

    123-15.fc42: noarch

    Source: sugar-read

Fedora 44

  1. Package sugar-read

    44 (Fedora 44) (Unspecified): A document reader for Sugar

    123-17.fc44: noarch

    Source: sugar-read

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.