Jelly's Manga Reading Thingy.
This is my own rendition of the excellent Mokuro project, made mostly just to do it. That being said, if you have any suggestions, please give me a heads-up and I will be happy to implement it. Probably.
Installation
To install, you should only need to run:
pip install comic-ocr-reader
Once that it is installed (it may take some time, there are large dependencies in there) you should then run:
comic_ocr_reader
Or if that doesn't work:
python3 -m comic_ocr_reader
Usage
- Prepare a folder containing the images you would like to process. As of v.0.0.1 the images in this folder must be named the page number you would like that image to be. (e.g. the PNG image you would like to use as the second page should be titled "2.png") The name of the folder will be the name of the resultant HTML file. (e.g. if your folder is titled "Naruto" the output HTML file will be "Naruto.html" )
- Run comic-reader-ocr and enter the "folder" command.
- Enter the absolute path of the folder from step 1 and wait for comic-reader-ocr to process all the images.
- Once finished, the resulting HTML file will be placed within the folder from step 1.
- Open the resulting HTML using your web browser of choice.
Notes
- You will need to keep the HTML file within the same folder as all the rest of the pages. Otherwise, the images will not load.
- Depending on your hardware, it may take quite some time to fully process all pages. On my laptop, it took roughly ~8s/page. I imagine on something with an actual GPU it would be faster though.
FAQs (as decided by Myself)
-
Is this a worse version of various other projects (e.g. Mokuro)?
- Yes.
-
Do you know how to like. Write things. That work?
- No.
-
Why did you do this?
- As a learning exercise, mostly. Plus, I like trying to reinvent wheels.
-
Can I make suggestions?
- Yes.
-
Did you use AI for this?
- Yes. Most of the HTML and JS was AI generated, as unfortunately I really really don't like looking at either of those things.
-
Are you going to try to make this a webapp because that probably makes a lot of sense or just. Like. Something that isn't Python so that it's easier to distribute or something?
- Yes. I'll probably try to rewrite this in Rust or do something like the mokuro-reader project.
Metadata
Release files for comic-ocr-reader 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| comic_ocr_reader-1.0.3.tar.gz | 15.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| comic_ocr_reader-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.6 kB
Release files / comic_ocr_reader-1.0.3.tar.gz
| Download URL | comic_ocr_reader-1.0.3.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88fffbf075452cf2904f516357838cca330e1a9f51347ab7a30c733068b5ed70
|
|
BLAKE2b-256 checksum How to use checksums |
7b69b561c63dec55a87081fc683c9bbdb993605859fd2828d00f01beff3efba0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 1, 2026.
Transparency logRelease files / comic_ocr_reader-1.0.3-py3-none-any.whl
| Download URL | comic_ocr_reader-1.0.3-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
452e6f9d0f5c3a3ed95499cccb80501a64ec8becba7b759acd92774a5699b7d7
|
|
BLAKE2b-256 checksum How to use checksums |
663b69d6e05be556dead9ab34730470f3a51790f757828e629a3181c7ac088fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 1, 2026.
Transparency log