Quote:
Originally Posted by Dave_S
Actually, my memory deceived me, so that was my bad.  The problem actually is in characters and not markup code. I set BD to the German language even when I am building English texts. I can not recall all the characters from memory, but the most recent one was "...". That is, three dots encoded as one character, usually used to indicate an interrupted sentence. When CoolReader comes to that character, it just totally gives up on the paragraph, at least in the implementation on the Hanlin V5. |
That is really strange! I have that "..." character in a lot of books and it shows up fine. Not really sure why it should be causing a problem.
usually when I have encountered problems in the past it has been things like the ampersand (&) issue - usually displays as the code " amp;" rather than &. When I create my FB2, I then open it in a text editor and do a 2-step find/replace, as follows:
(1) Find " amp; " (without quotes, of course) / Replace with " & "
(2) Find " amp;" / Replace with "&"
(1) first fixes things like "Smith & Co." where the & needs a space each side. (2) fixes the remaining instances of things like "R&R" (where no space is needed around the &).
The other issue I get is when there are non-Latin characters in the text - like Russian or Greek words. These tend to be display as the Unicode (I think) for symbols:
χρίστοζ = #967; #961; #943; #963; #964; #959; #950;
When there's just a few instances, I go in and change them manually in a simple text editor (Notepad in WinXP, TextEdit in Mac OS X). If there's a lot then that's a problem!
As you say, everyone is different, but I personally prefer the CoolReader interface and handling over FBReader on my BeBook - esp. the 3.0.19 port with the additional settings and search features. On the DR1000S FBReader is great! (especially for Mobi files). I liked OI when you had the choice, but it seems they have gone back to FBReader only? I guess they will "fix" that sometime soon.