MobileRead Forums - View Single Post

Jim Lester · 06-09-2011, 02:26 PM

At a first guess, I would think it has less to do with the embedded font, and more to do with the encoding of the CSS.

While the ePub 2 spec wasn't explicit on it, the CSS should be UTF8 encoded, but the whether or not the byte order marks are there shouldn't matter. So my guess is that there is something in the tool chain you are using that is outputting UTF8 that is causing RMSDK problems.

Have you tried editing CSS with non embedded fonts?

06-09-2011, 02:26 PM	#2
Jim Lester Evangelist Posts: 416 Karma: 14682 Join Date: May 2008 Location: SF Bay Area Device: Nook HD, Nook for Windows 8	At a first guess, I would think it has less to do with the embedded font, and more to do with the encoding of the CSS. While the ePub 2 spec wasn't explicit on it, the CSS should be UTF8 encoded, but the whether or not the byte order marks are there shouldn't matter. So my guess is that there is something in the tool chain you are using that is outputting UTF8 that is causing RMSDK problems. Have you tried editing CSS with non embedded fonts? Last edited by Jim Lester; 06-09-2011 at 02:28 PM. Reason: Correctness :)