MobileRead Forums - View Single Post - [Plugin] ePub3-itizer

AlPe · 12-02-2015, 08:01 AM

Great, thank you.

(Where do you prefer discussing about it? Here or on GitHub?)

At high level, what I would like to achieve is allowing Sigil users to create EPUB 3 Audio-eBooks (reflowable + Media Overlays) using Sigil.

To do that, there are several different entry points:

1. the user already has an EPUB 2 file (Open...)
2. the user creates the EPUB (2) file from scratch (New...)
3. the user has an EPUB 3 file already (Open...)

Cases 1. and 2. imply:

A. inserting suitable id's (actually <span id="...">) into the XHTML markup to denote the MO fragments (I plan to code a separate edit plugin for doing this automatically);
B. adding audio files into the container (Sigil can do this already);
C. adding the SMIL files into the cointainer (for now, assume they are "dummy" SMIL files, but they can be computed using my aeneas tool: http://www.readbeyond.it/aeneas/ );
D. outputting to EPUB3: this can be done with your plugin plus some modifications I can easily code.

Case 3. implies a slightly different D. step, since the original OPF might already be EPUB3 compliant e.g. by having EPUB3-specific metas. But I think that your current OPF converter can be modified to handle both EPUB2- or EPUB3- OPF files. For example, right now you create refines for dc:creator or dc:contributor, using ids like "create1" or "contrib2" etc. The original EPUB3 OPF might have those ids already.

My questions are:

a) since step D is almost already covered by your current plugin, does it make sense/are you fine with me adding functionalities to handle Media Overlays (SMIL) files to it, at least for cases 1. and 2.?

b) What would you suggest for case 3.? Is it better to wait for Sigil to become fully EPUB3-capable? Shall a specific version of the plugin be made for outputting EPUB3 if the user opens an EPUB3?

12-02-2015, 08:01 AM	#135
AlPe Digital Amanuensis Posts: 727 Karma: 1446357 Join Date: Dec 2011 Location: Turin, Italy Device: Several eReaders and tablets	Great, thank you. (Where do you prefer discussing about it? Here or on GitHub?) At high level, what I would like to achieve is allowing Sigil users to create EPUB 3 Audio-eBooks (reflowable + Media Overlays) using Sigil. To do that, there are several different entry points: 1. the user already has an EPUB 2 file (Open...) 2. the user creates the EPUB (2) file from scratch (New...) 3. the user has an EPUB 3 file already (Open...) Cases 1. and 2. imply: A. inserting suitable id's (actually <span id="...">) into the XHTML markup to denote the MO fragments (I plan to code a separate edit plugin for doing this automatically); B. adding audio files into the container (Sigil can do this already); C. adding the SMIL files into the cointainer (for now, assume they are "dummy" SMIL files, but they can be computed using my aeneas tool: http://www.readbeyond.it/aeneas/ ); D. outputting to EPUB3: this can be done with your plugin plus some modifications I can easily code. Case 3. implies a slightly different D. step, since the original OPF might already be EPUB3 compliant e.g. by having EPUB3-specific metas. But I think that your current OPF converter can be modified to handle both EPUB2- or EPUB3- OPF files. For example, right now you create refines for dc:creator or dc:contributor, using ids like "create1" or "contrib2" etc. The original EPUB3 OPF might have those ids already. My questions are: a) since step D is almost already covered by your current plugin, does it make sense/are you fine with me adding functionalities to handle Media Overlays (SMIL) files to it, at least for cases 1. and 2.? b) What would you suggest for case 3.? Is it better to wait for Sigil to become fully EPUB3-capable? Shall a specific version of the plugin be made for outputting EPUB3 if the user opens an EPUB3?