Thread: Monospace and other technical book formatting issues
View Single Post
Old 10-05-2020, 06:59 PM   #9
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by twowheels View Post
...so, I looked at the source for the image and saw that it referenced an svg file, so I unzipped the epub and see that the missing numbers are actually part of the svg, not some trick with overlapping text/image -- so it looks like it's actually a problem with the svg rendering.

EDIT: I've opened the svg in vim and it looks like the svg references an embedded font, "Times New Roman embedded", as well as some embedded glyphs for the 1, 0, ., and + symbols and the various bullets.

EDIT2: And if I browse to the unzipped media folder I see that none of the text in any of the svg files gets rendered.
Yup. Nanosvg doesn't support embedded text. See https://github.com/koreader/koreader...ment-703837152
pazos is offline   Reply With Quote