Re: Considering writing a proposal for the ePub filter for GSoC

Aah! At one time I thought dividing documents into separate files was mandatory, but then I checked and noticed we could use fragment identifiers. It seemed conceptually easier; I would be able to get ePub proof-of-concept exports working first and then work on document separation later down the line. Separate documents have hypothetical advantages in low-memory environments, such as the ereader tablets most likely to be processing ePub, since it wouldn't have to keep as big of a DOM tree in memory. I'm not sure if .zip supports solid compression but if it doesn't then we'd lose out a tiny bit on filesize. (I think the memory gains are more important than a few extra Kib here or there.) BTW are you a student? Or are you willing to mentor? --- On Tue, 4/5/11, Volodymyr Rudyj <vladimir.rudoy@gmail.com> wrote: > From: Volodymyr Rudyj <vladimir.rudoy@gmail.com> > Subject: Re: Considering writing a proposal for the ePub filter for GSoC > To: "David Wendt JR." <dcrkid@yahoo.com> > Cc: abiword-dev@abisource.com > Date: Tuesday, April 5, 2011, 11:40 PM > > 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:52:44 2011