Quote:
Originally Posted by DaleDe
Actually, since you can load your own fonts the code page can be disregarded. You simply pick a font that has the correct mapping in the font characters you want. The binary code of the characters determines what gets display. This is true for all 8 bit codes but if you support internationalization code set (Unicode, etc.) then things get a bit tricky. Most books, however, are not Unicode ready.
Dale
|
If Bookeen is going to support epub, then they will need to worry about Unicode. Here is an excerpt from the OPS spec:
"Publications may use the entire Unicode character set, using UTF-8 or UTF-16 encodings, as defined by Unicode (see
http://www.unicode.org/unicode/standard/versions). The use of Unicode facilitates internationalization and multilingual documents. However, Reading Systems are not required to provide glyphs for all Unicode characters.
Reading Systems must parse all UTF-8 and UTF-16 characters properly (as required by XML). Reading Systems may decline to display some characters, but must be capable of signaling in some fashion that undisplayable characters are present. Reading Systems must not display Unicode characters merely as if they were 8-bit characters. For example, the biohazard symbol (0x2623) need not be supported by including the correct glyph, but must not be parsed or displayed as if its component bytes were the two characters "&#" (0x0026 0x0023).
To aid Reading Systems in implementing consistent searching and sorting behavior it is required that Unicode Normalization Form C (NFC) be used (See http://www.w3.org/TR/charmod-norm/)."