On Tue, January 31, 2012 10:39 pm, Boris Schäling wrote:
...
1. My book is about C++. Unfortunately C++ is not a word - so e-readers
seem to break C++ wherever they like. A line could end with C+ or C,
and the plus sign(s) is on the next line. I turned C++ into
C#xfeff;+#xfeff;+ (which is already crazy as I don't know how often I
refer to C++ in my book). However this had some unfortunate side effects:
If
#xfeff; is used in the book title or titles which appear in the table of
contents, the Sony Reader displays rectangles (not in the body text
though).
#xFEFF; has a dual role as Zero Width No-Break Space and as the BOM.
Unicode 3.2 added #x2060, WORD JOINER, that is just a word joiner. [1]
The Unicode Standard says that you are supposed to use #x2060; in new
text, and that applications are supposed to support word joining with
either #x2060; or #xFEFF;.
Maybe, just maybe, your EPUB readers will do better with #x2060; than
they do with #xFEFF;.
Regards,
Tony Graham tgra...@mentea.net
Consultant http://www.mentea.net
Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
XML, XSL-FO and XSLT consulting, training and programming
[1] Page 5 (or 524) of http://www.unicode.org/versions/Unicode6.0.0/ch16.pdf
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
