I think I'm getting where the problem is. I'd still call it a bug of the newest eink-reader, which is why I'm adding more information here. I hope that some other PB owner can test this, and that I can point the PB support to this info.
So, in my PG books I use often this construct for footnote return anchors:
Code:
<div class="footnote"><a id="Footnote_1"></a>
<p class="foot"><a href="#FNanchor_1"><span class="label">(1)</span></a>
....
</p>
and I style it with css like:
Code:
.footnote .label { padding-right: 0.5ex; min-width: 4ex; margin: auto;}
Now, ebookmaker, the software which produces epubs at PG from posted html, adds, probably in error, this
tag attribute inside <a>. It appears that the combination of my css line for the
label class inside a
footnote container, plus the
tag addition, is fatal for eink-reader.
As a proof, I attach here three small epubs produced this way. 10001 which has both the css and the anchor crashes, 10007 and 10010 which have only one of them not.