MobileRead Forums - View Single Post

rsperberg · 01-27-2006, 01:27 PM

I'm willing to concede your technological point, but I'm not sure why what you say is true.

Is it because the single XML file is kept in memory?

How does making the file "precomiled" help?

I know that in the case of the FBReader, it reads zipped versions of FB2 files, so that would make the books smaller in the e-reader than in the human readable XML version (I think. Am I wrong here?).

And it looks to me like the distinct sections of the FB2 file -- description, body, binary -- could be taken advantage of in the same way that separate files could.

As for that matter, I'm not sure FBReader keeps all of a book in memory in DOM, but instead I think it uses SAX, which doesn't require a lot of memory. Would this impact your conclusions at all?

Well, you were speaking of the format. I have learned nothing that would contradict your statement that it wasn't designed with handhelds in mind.

Still, the FBReader runs on Sharp Zaurus, Siemens Simpad and Nokia 770. And the Haali Reader runs on PocketPC, Win CE 2.11, 3.0 and .NET, and WM2003. While I have experienced low-memory conditions on my Nokia 770, they have always been occasioned by Opera; I haven't seen that come up with FBReader.

I appreciate your taking the trouble to explain these issues to me.

Thanks,

Roger

01-27-2006, 01:27 PM	#4
rsperberg Zealot Posts: 114 Karma: 10 Join Date: Jun 2005 Location: NJ Device: Kindle Voyage	I'm willing to concede your technological point, but I'm not sure why what you say is true. Is it because the single XML file is kept in memory? How does making the file "precomiled" help? I know that in the case of the FBReader, it reads zipped versions of FB2 files, so that would make the books smaller in the e-reader than in the human readable XML version (I think. Am I wrong here?). And it looks to me like the distinct sections of the FB2 file -- description, body, binary -- could be taken advantage of in the same way that separate files could. As for that matter, I'm not sure FBReader keeps all of a book in memory in DOM, but instead I think it uses SAX, which doesn't require a lot of memory. Would this impact your conclusions at all? Well, you were speaking of the format. I have learned nothing that would contradict your statement that it wasn't designed with handhelds in mind. Still, the FBReader runs on Sharp Zaurus, Siemens Simpad and Nokia 770. And the Haali Reader runs on PocketPC, Win CE 2.11, 3.0 and .NET, and WM2003. While I have experienced low-memory conditions on my Nokia 770, they have always been occasioned by Opera; I haven't seen that come up with FBReader. I appreciate your taking the trouble to explain these issues to me. Thanks, Roger