i did change the font and the glitch did disappear, that is why I reported it as bookerly specific; and I checked other books and checked the book source code to eliminate it being book-specific.
but it would actually be some interaction between the font and the renderer ? , as it has to be that exact combination of a speech mark followed by a capital C or K
here is the reddit link, which has a helpful image showing the exact issue:
https://www.reddit.com/r/kindle/comm...acing_issues/?
and the older mobileread thread:
http://www.mobileread.mobi/forums/sh...=262979&page=3
that thread blames kindle firmware
i have not as yet checked for any firmware update for the kindle voyage, i keep it mostly in aeroplane mode - but I can go do that...
...sync finds nothing new - I have firmware 5.6.5.(27303000038) , which is at least one update on from when I bought the kindle last year
UPDATE - the plot thickens- that old thread is discussing converted + sideloaded books which is also what I was using. so I just skipped through a couple of recently-bought-from-amazon books and in those the
"C construct is fine.
so there is some other factor involved ?
also, much of that old thread is about the complexities of emailing books via amazon, whereas I am using only USB to get azw books from calibre to voyage. I did try converting to mobi instead, with one test book and observed the same issue, in bookerly.
here is a code example from a sideloaded book where I do see the bug, in bookerly:
<p class="tx">“Can I see it?” Jaynie asks.</p>
where the CSS class declaration is
.tx {
display: block;
font-size: 1em;
font-style: normal;
font-variant: normal;
font-weight: normal;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
margin-top: 0;
text-align: justify;
text-indent: 1.5em;