Quote:
Originally Posted by shalym
Give me your tired, your poor...
Shari
|
This is a surprisingly long thread, started quite a while back.
I'm working on a PHP-based server side epub3 reader/displayer that will show epub3 documents to visitors WITHOUT requiring the visitor to install anything or download anything. The server side administrator will have to unzip the epub3 inside the DOCUMENT_ROOT of a website. The rest will happen automagically. TOC navigation will appear as needed. Text and images will flow around it.
I'm pretty close. Perhaps in another two months of part time work I'll have a freeware version to look at. I see this as a marketing tool. It will allow casual visitors to read all or perhaps a selected set of pages only. If they like what they see they can buy and download the full epub. And then view it with what ever software they choose to install.
Or they can continue to read it online. As they wish. This will be particularly useful to me, as I publish lengthy how-to-do-it boat building pages on the net. epub3 format will enhance my reader's experience.
=====================
I have a question. I've been poking around the net and I've been reading. Haven't found the answer yet. My TOC generation codes start by parsing the package.opf file, which is present and required for all epub3 compliant documents.
However. I downloaded about two dozen public domain epub3 example documents to work with. And package.opf is sometimes found in OPF/package.opf and sometimes as EPUB/package.opf.
My codes can test both paths and work with where ever package.opf is found. But something is going on I don't understand yet.
I'll have to spend a few nights reading the OPF specs I guess. Help me with this if you can. Why is epub3 sometimes organized one way, and other times the other?