View Single Post
Old 12-05-2013, 01:09 PM   #17
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,432
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by tshering View Post
I cannot see that davidfor says this. I take his statement as implying that he first had a certain suspicion in this direction. and did not found supporting evidence. If the problem were related to the font, one would rather expect to see squares or question marks or empty spaces.
The ACCESS renderer seems to look for missing characters in other installed fonts. The issue being is that they tend to be shown at a very small font size. This is different from the RMSDK renderer which will use the squares (blank, X or ?).

When I tried François' test kepub.epub and removed the extraneous toc.ncx entry, the display looked fine with 3.1.0 but the Chinese character showed up as 1/3 the size of the other characters until I switched the font to a font that supported that character (Code2000, Ryumin, Gothic).

Regards,
David

Last edited by DNSB; 12-05-2013 at 01:16 PM.
DNSB is offline   Reply With Quote