Upstream software project

enca

Detects encoding of text files

About enca

Detects encoding of text files

This project links 11 native package records across 3 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

Debian 13 (Trixie): 3 package records; openSUSE Leap 16.0: 4 package records; openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.enca: recorded package coverageDebian 13 (Trixie)3 recordsopenSUSE Leap 16.04 recordsopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
enca
Publisher
Not authoritatively mapped
Native package records
11
Operating systems
debian-13, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-only
Source repository
Not reported

Source-reported description

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

Enca is an Extremely Naive Charset Analyser. It detects character set and encoding of text files and can also convert them to other encodings using either a built-in converter or external libraries and tools like libiconv, librecode, or cstocs. Currently, it has support for Belarussian, Bulgarian, Croatian, Czech, Estonian, Latvian, Lithuanian, Polish, Russian, Slovak, Slovene, Ukrainian, Chinese, and some multibyte encodings (mostly variants of Unicode) independent on the language. This package also contains shared Enca library other programs can make use of. Install Enca if you need to cope with text files of dubious origin and unknown encoding and convert them to some reasonable encoding.

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.

Debian 13 (Trixie)

  1. Package enca

    trixie (Debian 13 (Trixie)) (text): Extremely Naive Charset Analyser - binaries

    1.19-3: amd64 arm64

  2. Package libenca0

    trixie (Debian 13 (Trixie)) (libs): Extremely Naive Charset Analyser - shared library files

    1.19-3: amd64 arm64

    Source: enca

  3. Package libenca-dev

    trixie (Debian 13 (Trixie)) (libdevel): Extremely Naive Charset Analyser - development files

    1.19-3: amd64 arm64

    Source: enca

openSUSE Leap 16.0

  1. Package enca

    leap-16.0 (openSUSE Leap 16.0) (Productivity/Other): Detects encoding of text files

    1.19-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: enca

  2. Package enca-devel

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/C and C++): Header files and libraries for Enca development

    1.19-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: enca

  3. Package libenca0

    leap-16.0 (openSUSE Leap 16.0) (System/Libraries): Header files and libraries for Enca development

    1.19-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: enca

  4. Package libenca0-32bit

    leap-16.0 (openSUSE Leap 16.0) (System/Libraries): Header files and libraries for Enca development

    1.19-160000.2.2: x86_64

    Source: enca

openSUSE Tumbleweed

  1. Package enca

    tumbleweed (openSUSE Tumbleweed) (Productivity/Other): Detects encoding of text files

    1.19-2.14: x86_64

    Source: enca

  2. Package enca-devel

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/C and C++): Header files and libraries for Enca development

    1.19-2.14: x86_64

    Source: enca

  3. Package libenca0

    tumbleweed (openSUSE Tumbleweed) (System/Libraries): Header files and libraries for Enca development

    1.19-2.14: x86_64

    Source: enca

  4. Package libenca0-32bit

    tumbleweed (openSUSE Tumbleweed) (System/Libraries): Header files and libraries for Enca development

    1.19-2.14: x86_64

    Source: enca

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.