View Single Post
Old 06-15-2009, 01:45 PM   #56
netseeker
sleepless reader
netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.
 
netseeker's Avatar
 
Posts: 4,763
Karma: 615547
Join Date: Jan 2008
Location: Germany, near Stuttgart
Device: Sony PRS-505, PB 360° & 302, nook wi-fi, Kindle 3
As a software developer i've to admit that i wouldn't implement a (X)HTML-parser (as well as a much simpler parser for DTBook based documents) if i would have to implement a ePub2SomethingElse converter. I would just scan the manifest for all required files of the publication as Valloric pointed out.
If i would have to implement a ePub renderer then i would parse and interpret all permitted media elements contained in the xhtml or dtbook files. But if a used media type isn't one of the OPS core media types and my application (or the device) is not able to support that certain media type, then i would have to read the manifest because according to the specification the manifest must contain an alternative fallback for that media then.
netseeker is offline   Reply With Quote