Hi!
I`m investigating this idea too.
> We are allowed to use fragment identifiers in our manifest, so we wouldn't have to split documents into separate HTML files.
It seems to me that it`s better to create separate files for every
chapter for user convenience - when chapters are rather small it is
easier to reading software to parse and load it (don`t sure how much
performance this will give, but we should`n ignore it - at least we
should give user an option that will enable or disable dividing
document into separate files).
> Judging by the existence of HTML export functionality (IE_Exp_HTML) it's tempting to add some options to it and/or write an ePub subclass that uses the HTML functionality to generate the ops files.
Yes, it could be used. Though in my export filter prototype I`m using
my own export classes to better understand how exporter works, it`s
use can reduce lot`s of work with OPS, of course with some
modifications. Then the only thing we need is to created packaging
file (.OPF) and add some container metadata (container.xml in
META-INF).
Sincerely,
Volodymyr Rudyj
Received on Wed Apr 6 05:40:46 2011
This archive was generated by hypermail 2.1.8 : Wed Apr 06 2011 - 05:40:46 CEST