View Single Post
Old 07-12-2015, 02:57 AM   #1
AcidWeb
KCC Co-Author
AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.
 
AcidWeb's Avatar
 
Posts: 845
Karma: 765434
Join Date: Mar 2013
Location: Poland
Device: Kindle Oasis 2
HD_CONTAINER anomalies

I have two image heavy EPUB files.
A - 2,38 MB - Image resolution: 758x1024 (PW1/2)
B - 3,93 MB - Image resolution: 1072x1448 (PW3/Voyage)

There are only two differences between them:
  • image resolution
  • original-resolution meta property field
When I convert them using KindleGen V2.9 build 1029-0897292 with -dont_append_source option size of output is strage...

A.mobi - 2,50 MB - This is OK.
B.mobi - 6,92 MB - Bloated like hell.

After further examination I discovered that HD_CONTAINER is added to B.mobi. For some reason it contain another copy of the same images, with the same resolution. Complete waste of space.

Headers:
A
B

It is not connected to input file size so I guess there is some boundary resolution that trigger creation of HD_CONTAINER. Additionally I experimented with original-resolution field but not found any connection with HD_CONTAINER creation.

Anybody researched this matter? Any idea how to strip HD_CONTAINER or modify EPUB so that container would not be created?

Last edited by AcidWeb; 07-12-2015 at 03:20 AM.
AcidWeb is offline   Reply With Quote