Plato: A document reader for PDF, ePUB, DjVu, etc.

[baskerville]

Plato is a document reader for Kobo's e-readers.

It was tested on the following devices:

• Clara BW.
• Elipsa 2E.
• Clara 2E.
• Libra 2.
• Sage.
• Elipsa.
• Nia.
• Libra H₂O.
• Forma.
• Clara HD.
• Aura H₂O Edition 2.
• Aura Edition 2.
• Aura ONE.
• Glo HD.
• Aura H₂O.
• Aura.
• Glo.
• Touch C.
• Touch B.

Any 4.X.Y firmware, with X ≥ 6, will do.

I wrote a guide and a manual.

If you're looking for an english dictionary, you might be interested in my custom version of WordNet 3.1: place wn-xml.* in the dictionaries directory and dictionary-user.css in the css directory.

You can convert StarDict dictionaries using sdunpack (pre-built binaries are available for Linux, macOS and Windows).

[pdurrant]

Looking at the github repository:

plato is a document reader for Kobo's e-ink devices.

It was tested on a Glo HD and an Aura ONE.

[compurandom]

Binaries? Install instructions??

[doubleshuffle]

I think I'll give this a pass until non-programmers like me can install it without having to spend a whole day on it.

[pdurrant]

Moved to the dev forum

[kyteflyer]

I was interested until I looked at the guide and realised that I just cannot be bothered with so much fiddling.

[Ken Maltby]

There is a plato.sh that you would have after moving the plato folder into .adds. You could try running that from KSM.

Luck;
Ken

[geek1011]

Great job on the reader so far! You may want to improve the build and fmon docs, as it took me about 20 mins to get this to build, and another 15 to get this to work (including reading the source for some info not in the docs), and I already have experience with this kind of thing.

[baskerville]

Originally Posted by geek1011

You may want to improve the build and fmon docs, as it took me about 20 mins to get this to build, and another 15 to get this to work (including reading the source for some info not in the docs), and I already have experience with this kind of thing.

Thanks for trying and congratulations.

I'd like to known what was missing from the docs: it would be great if you could find the time to create issues on the GitHub page.

Although this reader is built around the idea of having good, easily modifiable metadata, I'm going to give a hint on how to speed up the initial import process: the steps involving the -S and -R flags can be skipped.

[geek1011]

Originally Posted by baskerville

Thanks for trying and congratulations.

I'd like to known what was missing from the docs: it would be great if you could find the time to create issues on the GitHub page.

Although this reader is built around the idea of having good, easily modifiable metadata, I'm going to give a hint on how to speed up the initial importation process: the steps involving the -S and -R flags can be skipped.

Ok. I don't have much time right now, but I'll submit a pr later.

A few quick things here:
- In the guide, the cargo --feature flag is actually --features, I think that was a typo.
- It is unclear where the libs dir goes, the only way I found it was by looking at the gitignore file, and creating it.
- It would be nice to have static builds (but I don't know enough about your code yet to see if it is possible, and I don't know much rust).
- In English, it is not importation (bad grammar), it is importing.
- For most people who follow the guide, it is unclear whether the importing step is required, and if you don't do the importing step, the reader appears to crash, with a error message in the log (which most people wouldn't understand).
- It would be good to add uninstallation instructions (from reading the code, it seems like all you need to do is delete the .adds and icons folder, because you added checks, great job on this part -- I like the design of the scripts)
- It took a few mins to figure out the required deps, maybe say what debian packages to install
- It would be nice to make an automated makefile for building.
- A few more things, mostly about the same topic

By the way, your code looks nice and well designed.

Hint: some screenshots would be nice, I couldn't wait to try it (I love all ebook related software).

[taos]

Can I ask which operating system / distribution you used to successfully compile plato?

With arch linux (packages for rust/rustup, libmupdf, djvulibre installed) I get stuck when I build the importer, with Kubuntu 16.04 LTS (rustc, cargo, libdjvulibre21, libdjvulibre-dev, libmupdf-dev installed) even earlier when I try to build the mupdfwrapper.

I'm not familiar with rust so I guess I overlooked something.

Installation on the Kobo with the files from plato.zip worked fine, I can start plato either via fmon from nickel or by a script I wrote and put in the userscript folder of KSM. Unfortunately, plato crashes immediately because there's no database yet (at least, that's what the crash.log suggests). Running

plato -Z /mnt/onboard/.test

directly on the Kobo (either from KSM's kbterminal or from script) doesn't work because it seems that plato can't find the libmupdf.so library (error message from kbterminal).

[geek1011]

Originally Posted by taos

Can I ask which operating system / distribution you used to successfully compile plato?

With arch linux (packages for rust/rustup, libmupdf, djvulibre installed) I get stuck when I build the importer, with Kubuntu 16.04 LTS (rustc, cargo, libdjvulibre21, libdjvulibre-dev, libmupdf-dev installed) even earlier when I try to build the mupdfwrapper.

I'm not familiar with rust so I guess I overlooked something.

Installation on the Kobo with the files from plato.zip worked fine, I can start plato either via fmon from nickel or by a script I wrote and put in the userscript folder of KSM. Unfortunately, plato crashes immediately because there's no database yet (at least, that's what the crash.log suggests). Running

plato -Z /mnt/onboard/.test

directly on the Kobo (either from KSM's kbterminal or from script) doesn't work because it seems that plato can't find the libmupdf.so library (error message from kbterminal).

I used Debian sid. For the mupdf wrapper, make sure you adjust the path in the command. I also had problems with the distro package for mupdf, so I build it from source into a temp folder, then copied the lib.

[jcn363]

Two bricks hear.
I think... a step by step, how-to, doc... is needed or perhaps

Good luck.

[baskerville]

Originally Posted by taos

Running

plato -Z /mnt/onboard/.test

directly on the Kobo

The binary that ships in the archive is the reader: it doesn't take any argument.

I'm working on simplifying all this: it would probably make more sense for the reader to do a quick import (equivalent to plato -I) if the database is missing.

Bear with me!

[jcn363]

Originally Posted by baskerville

Bear with me!

Don't worry, I'll don't give up!

Good luck.