translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
application
    jbig2dec0.13
    Qmaf3iU2XYZuBe5aWUogooZ48gKznvWiMaEKj5DX2Qg5Mm
    5dtWvkFpHX4fLhLqoHZRDQVtbqKoo8
      Qmaf3iU2XYZuBe5aWUogooZ48gKznvWiMaEKj5DX2Qg5Mm
      5dtWvkFpHX4fLhLqoHZRDQVtbqKoo8

      • Details
      • Run
      • Build
      • Files
      • History
        • Website

          http://www.ghostscript.com/jbig2dec.html

          License

          • GPL 3.0

          Environment

          linux

          Architecture

          x86-64

          jbig2dec is a decoder implementation of the JBIG2 image compression format.

          JBIG2 is designed for lossy or lossless encoding of ‘bilevel’ (1-bit monochrome) images at moderately high resolution, and in particular scanned paper documents. In this domain it can be very efficient, offering compression ratios on the order of 100:1.

          This is a decoder only implementation, and its primary use is in Ghostscript and MuPDF for decoding JBIG2 streams in PDF files. Thus its primary focus is the set of JBIG2 features supported in PDF.

          The specification has been published as ISO IEC 14492 and ITU T.88. These documents completely describe the format and they’ll be required if you want to understand the code and contribute. We prefer the ISO version but have not discovered significant differences between the two.

          JBIG2 also includes the CCITT T.4 and T.6 (group 3 and group 4) fax encodings, which are documented separately. Their specifications and T.88 can be obtained from the ITU. The ISO version of JBIG2 can be obtained through the ISO website.

          Unfortunately, none of these documents are free, though the ITU sometimes offers free download specials. More information about JBIG2 and a copy of the draft spec are available from the JPEG website.

          Versions

          • 0.13

          Related

          • maintainer

            occam

          DependenciesHelp

          This section shows a list of objects the current object is dependent upon in order to be used.

          For dependencies that are only relevant as part of the build or runtime of the object, it is best to describe those local to those sections.

          • library

            png

            1.x

          BuildHelp

          This section tracks information useful to describing how to build this object.

          Dependencies

          • collection

            build

            1.0

          • compiler

            g++

            >5

          • application

            m4

            >=1.4

          • collection

            autoconf

            2.x

          • collection

            automake

            1.x

          • application

            libtool

            2.x

          Resources

          • jbig2dec-0.13.tar.gz

            application/gzip

            GhostScript jbig2dec 0.13 Source Code

            http://downloads.ghostscript.com/public/jbig2dec/jbig2dec-0.13.tar.gz

            QmYF24yF1URVyAzSCcwbsncdw5aYpVUJAt8X7G5t1ubpST

            QmPvUd1oFW787ZmGd7eMuFUypXHKPLP2dqLDE7QCGdSHKp

            QmUSc5BLoouFKDMS8S2x8Q832A6H5JJyRVjzg3CeSKLSqv

            download

          Command

          • /bin/bash
          • build.sh

          Build Environment

          • linux
          • x86-64

          RunHelp

          This section tracks information useful to describing how to run this object.

          Command

          • /usr/bin/jbig2dec

          Run Environment

          • linux
          • x86-64

          InstallationHelp

          Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

          This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

          There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

          ActionSourceDestinationSummary
          Linkusr/lib/usr/lib

          N/A

          Linkusr/include/usr/include

          N/A

          Linkusr/share/usr/share

          N/A

          Linkusr/bin/usr/bin

          N/A

          No files will be installed.

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?