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

[baskerville]

Originally Posted by TheRealJohnAdams

Am I right to believe that Plato, like KOReader, uses a pure directory-style categorization system?

Prior to 0.8.5, Plato was using hierachical categories.

It was decided in #96 to use directories as the sole categorization mechanism.

I guess you could use hard links (not an easy thing to do on FAT32!), but it wouldn't be enough, I'd also need to add the ability for a database entry to have multiple paths.

[TheRealJohnAdams]

I see. That's very disappointing, but thank you for the reply. Incidentally, another post by me may appear at some point. It was delayed pending moderator approval (either because it was a double post or because it contained a link) that represents my attempt at figuring out the (apparently now-removed) categories feature; because there is no longer a categories feature, it is irrelevant.

[baskerville]

I've released 0.8.6.

@NiLuJe: I'm now shipping a unified plato.sh (and nickel.sh) inside the plato-VERSION.zip archive.

[NiLuJe]

@baskerville: Got it, thanks for the heads up .

[alicskywalker]

Awesome work baskerville, really like the clean look of it!

Just a question, for the highlights I made in Plato, how do I see them on my computer?

[baskerville]

Originally Posted by alicskywalker

For the highlights I made in Plato, how do I see them on my computer?

You could make a backup of your library and use the emulator to open books within that library.

[baskerville]

I've released 0.8.7.

[baskerville]

I've released 0.8.8.

[favero_]

Congratulations on the project, Plato is awesome! Quick question - I cannot find .dict.dz dictionaries, only .tar.bz2 and I cannot find any places to convert them... What should I do? Is there a plan for the future to release bz2 support? Or does it support and I'm not knowing how to make it work?

Thanks,

[baskerville]

Originally Posted by favero_

I cannot find .dict.dz dictionaries, only .tar.bz2 and I cannot find any places to convert them...

.tar.bz2 isn't a dictionary format but a compressed tar archive.

From my experience, the StarDict format is the most frequent. You can convert from StarDict to dictd via sdunpack.

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

[jsessions]

Out of interest why does the plato.png file need its own directory (icons)... why not just save it to root like other launchers; KFMon, KOreader, CoolReader etc.

I appreciate it's a minor point but I like things to be streamlined

[boriar]

Originally Posted by jsessions

Out of interest why does the plato.png file need its own directory (icons)... why not just save it to root like other launchers; KFMon, KOreader, CoolReader etc.

I appreciate it's a minor point but I like things to be streamlined

You can put the png file wherever you want. The icons directory isn't mandatory.

You only need to change the line:
filename = /mnt/onboard/icons/plato.png

in .adds\kfmon\config\plato.ini

[jsessions]

Originally Posted by boriar

You can put the png file wherever you want. The icons directory isn't mandatory.

You only need to change the line:
filename = /mnt/onboard/icons/plato.png

in .adds\kfmon\config\plato.ini

Thanks for this info.

[baskerville]

@NiLuJe Please feel free to fix the aforementioned discrepancy. I think it would be cleaner to have all the icons in a directory but I'm fine with any other consistent scheme. I've added plato.png to the repository (in the artworks directory).

[NiLuJe]

Unfortunately, moving the icons will require properly removing existing icons, and while I can certainly do that in the OCP install script, that leaves people doing stuff manually in the lurch, because that's one more step to add to avoid having duplicate images, one of which won't actually do anything anymore .

TL;DR: That's probably not going to happen. If it seriously tickles someone's OCD, fixing it manually is trivial, as mentioned earlier.
But as a general default, it's a bit too late for that, unfortunately. And I'm wary of making the install script be a special snowflake in how it lays stuff out.

(It never personally bothered me, because I have nothing in the root folder short of, well, folders, so I didn't really think about it, but, yeah, in hindsight, I should have moved everything in a folder way back when).