gocr mit Homebrew, apt, dnf, MacPorts, Nix, pacman, zypper installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• gocr
• gocr.tcl

Projektgeschichte

The official GOCR page says Schulenburg started the program, led the SourceForge developer team, and continued maintaining the package at a low time base after 2010. The site explains the dual naming: the program's original and internal name is GOCR, while the SourceForge project used JOCR because the gocr project name was unavailable there.

The SourceForge-era history is visible in the official news stream: 0.3.0 appeared in December 2000, libgocr was made publicly available in April 2001, 0.37 arrived in August 2002, and the 0.40 through 0.49 series carried the project through the 2005 to 2010 period. Later releases 0.50, 0.51, and 0.52 were announced from the maintainer site rather than always being uploaded to SourceForge.

Adoptionsgeschichte

GOCR's adoption pattern is classic pre-GitHub free software: SourceForge hosting, CVS development, tarball releases, mailing-list support, and downstream packaging. The official download page mentions RPMs, Debian packages, Windows binaries, OS/2 packages, and SourceForge source tarballs.

The batch package metadata lists GOCR in Homebrew, Debian, Fedora, MacPorts, Nix, Arch, Ubuntu, and openSUSE package sets. That broad downstream footprint matters more than upstream velocity: OCR users and scanning frontends kept relying on a small C command-line engine that packagers could build and ship.

Wie es verwendet wird

GOCR is used from the command line to read supported image formats and emit text. The official page notes that it can be used with different frontends and can open many image formats, with additional formats handled through external tools such as NetPBM.

The project is best understood as a lightweight OCR engine and utility for scanned text, not a modern machine-learning OCR stack. It is most useful where scriptability, old-format support, and small dependency surfaces matter.

Warum Paket-Nerds sich dafür interessieren

Package nerds care about GOCR because it is a living fossil of early SourceForge packaging culture: CVS, tarballs, distro patches, optional graphical frontends, and long-lived formulae. It shows how a quiet C utility can survive for decades because it is easy for distributions to keep carrying.

Its GOCR/JOCR naming split is also a small lesson in package identity: upstream command names, project-hosting names, tarball names, and distro package names do not always line up cleanly.

Zeitleiste

• 2000-06: SourceForge hosting began for the JOCR project, according to the official page.
• 2000-12: GOCR 0.3.0 announced.
• 2001-04: libgocr public beta announced.
• 2005-03: GOCR 0.40 released.
• 2010-09: GOCR 0.49 released.
• 2013-03: GOCR 0.50 released.
• 2017-08: GOCR 0.51 released.
• 2018-10: GOCR 0.52 released.

Related projects

• libgocr was the related API/library effort documented on the official site.
• NetPBM is an important companion dependency for broader image-format handling.
• Kooka, XSane, and other scanning frontends are adjacent tools that historically used command-line OCR engines.

Quellen

• https://formulae.brew.sh/api/formula/gocr.json
• https://jocr.sourceforge.net/
• https://jocr.sourceforge.net/developers.html
• https://jocr.sourceforge.net/download.html
• https://sourceforge.net/p/jocr/code/
• https://sourceforge.net/projects/jocr/rss?path=/gocr