MobileRead Forums - View Single Post

bobcdy · 12-16-2013, 09:29 PM

Normally I haven't had trouble enbedding unicode characters, but this time I'm working with text that includes Latin Exended Additions (for example with K, S, H etc that have a period underneath the letters. My reader is the Nook ST with Mantano epub reader, and the fonts I'm embedding are CharisSil that contain these unicode additions. The only way I've been able for force Mantano to show these unicode extended characters is to add the CharisSil fonts to the Mantano font subdirectory in addition to embedding the font in my body text tag. Previously when I embedded a font, all the characters of the font such as all the small caps showed correctly in Mantano without also adding the small caps font to the Mantano font subdirectory.

Such a situation means that anyone else reading my epub will need to also add the CharisSil fonts to their ereader sub-directory in order to see the extended characters - I'd like to avoid this.

Does anyone know if this behavior is typical of unicode extended, or am I improperly coding the xhtml?

12-16-2013, 09:29 PM	#1
bobcdy Fanatic Posts: 527 Karma: 1048576 Join Date: May 2009 Device: bebook; prs-950; nook simple touch; HTC Jetstream tablet	epub problem with unicode extended Normally I haven't had trouble enbedding unicode characters, but this time I'm working with text that includes Latin Exended Additions (for example with K, S, H etc that have a period underneath the letters. My reader is the Nook ST with Mantano epub reader, and the fonts I'm embedding are CharisSil that contain these unicode additions. The only way I've been able for force Mantano to show these unicode extended characters is to add the CharisSil fonts to the Mantano font subdirectory in addition to embedding the font in my body text tag. Previously when I embedded a font, all the characters of the font such as all the small caps showed correctly in Mantano without also adding the small caps font to the Mantano font subdirectory. Such a situation means that anyone else reading my epub will need to also add the CharisSil fonts to their ereader sub-directory in order to see the extended characters - I'd like to avoid this. Does anyone know if this behavior is typical of unicode extended, or am I improperly coding the xhtml? Last edited by bobcdy; 12-16-2013 at 09:51 PM.