|
Thanks for the replies.
The character in the original Word document that appears as a space is non-breaking space, (Unicode character 00A0, as opposed to 0020), and that is why I was confused when the Android ePub renderer was treating it as if it were a breaking space (even though the iPhone renderer, iBooks, was treating it properly).
My confusion was whether it was a conversion problem or whether it was resultant from the ePub reader I was using. I have been using Moon+ as my tester, which jackie suggests isn't always true to the internal CSS. So I will try one of the alternatives and see what happens.
Is there any way to confirm what the actual Unicode character included in the final ePub CSS is? Can I be confident that the 00a0 character that was in the original Word document made it to the ePub, and any other error is on the part of the reader?
|