Overview
didjvu uses the Gamera framework to separate foreground/background layers, which can be then encoded into a DjVu file.
Prerequisites
The following software is required:
Python 3 (≥ 3.6)
Gamera-4 (≥ 4.0)
DjVuLibre (≥ 3.5.22)
minidjvu (≥ 0.8) for the --pages-per-dict/-p option
Additionally, one of the following libraries is needed for the --xmp option:
Installation
The easiest way to install didjvu is from PyPI:
pip install didjvu
Alternatively, you can use didjvu without installing it, straight out of an unpacked source tarball or a VCS checkout.
It’s also possible to install it from source for the current interpreter with:
pip install .
The man pages can be deployed using:
make install_manpage
By default, make install_manpage installs them to /usr/local/. You can specify a different installation prefix by setting the PREFIX variable, e.g.:
make install PREFIX="$HOME/.local"
About this fork
This repository is a port of the original repository to Python 3.
The process involved the 2to3 tool and manual fixes afterwards to get the existing tests to pass. Some of the error reports and fixes arising from the early porting process have been contributed by @rmast.
At the moment there are no plans to submit a pull request to the upstream repository, which would probably require some changes to my code as well. This is mostly due to the corresponding upstream issue being marked as wontfix: Issue #13.
I will try to keep this fork/port in sync with the upstream changes where necessary. Please note that I do not have any plans on implementing completely new features for now. Feature requests and bugs which can be reproduced in the original version as well should be reported at both places in the best case.
Differences from upstream
Package requires Python ≥ 3.6. * Please note that Python 3.6 support has been dropped here in the meantime and the latest code might stop working on EOL Python versions.
Drop old Gamera workarounds.
Migrate from nose to plain unittest stdlib module.
Conform to PEP8 coding style.
Use standardized setup.py-based installation.
Rename lib to didjvu and migrate didjvu binary to __main__.py and console script version.
Release files for didjvu 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| didjvu-0.11.0.tar.gz | 49.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| didjvu-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 94.1 kB
Release files / didjvu-0.11.0.tar.gz
| Download URL | didjvu-0.11.0.tar.gz |
|---|---|
| Size | 49.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b47899005749096fc1a301eaddecddafbb15b9d1b032743bf90ce702c2d55b17
|
|
BLAKE2b-256 checksum How to use checksums |
b6935da280e8853649a5cabf6512785fb96747c3e5461d25fdd37cf28460d192
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 7, 2025.
Transparency logRelease files / didjvu-0.11.0-py3-none-any.whl
| Download URL | didjvu-0.11.0-py3-none-any.whl |
|---|---|
| Size | 44.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73f5188cbb503c15585c349a1ad9b752d749cf4157000318d7067347069c5ea8
|
|
BLAKE2b-256 checksum How to use checksums |
1621af25c80dc37712633697b2b49df20fa92fb8086dfbba812798c796cde134
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 7, 2025.
Transparency log