[KevinH]

As DiapDealer said, there is nothing KindleUnpack can do. But with some very slight css modifications to your Berenstain epub, you can fix the issue.

If you modify OEBPS/Styles/style0001.css

And after modifying the following two css rules, it all appears to work at least for some font layout engines:

p.copyright {
  font-size: 28%;
  line-height: 75%; /* was 118% */
  margin-bottom: 0;
  margin-top: 0;
  text-align: center;
  text-indent: 0;
  letter-spacing: -0.5px;  /* added */
}



div.page3_item1 {
  left: 49.22%;
  position: absolute;
  right: 0;
  top: 43.5%; /* was 44.5% */
}

So you can compensate for the difference between the Kindle font layout engine and Calibre's or Sigil's QtWebEngine font engine with just very slight css modifications.

I am sure any other anomalies inside that epub can be fixed in a similar manner. And I am sure the same thing holds for the other Noah epub but since I did not have a version of it, I could not given you hints as to where to fix them.

Unfortunately the scrambled versions of the azw3s even scrambled the images and thus were next to useless especially given the problem was not in KindleUnpack.

Hope this helps.