FBReader on N770 -- 0093, 0094, & 0097

[Mike G.]

Hi folks!

I just installed FBReader on my Nokia N770. Great app!

I'm using it to read Mobipocket files, and it's working very well
except for one minor
encoding (?) glitch.

Some characters are showing up as boxed 0093 (in a box, 00 on top, 93
on bottom), 0094, or 0097.

I downloaded the extra encodings pack, and restarted the device, but
that didn't fix the problem.

Any ideas?

The 0093 and 0094 show up on "Warp Point" from www.fictionwise.com,
which unfortunately not
free.

But the 0097 shows up on "Freehold" from the Baen free library at
www.baen.com.

Does anyone have any suggestions as to how I can fix this?

The boxes aren't stopping me from reading, but they are a bit
unpleasant.

Thanks!

Mike G.

[Marius Gedminas]

On Sun, Jul 01, 2007 at 11:51:42AM -0000, Mike G. wrote:
> I just installed FBReader on my Nokia N770. Great app!
>
> I'm using it to read Mobipocket files, and it's working very well
> except for one minor
> encoding (?) glitch.
>
> Some characters are showing up as boxed 0093 (in a box, 00 on top, 93
> on bottom), 0094, or 0097.

There are two possible reasons for this:

* you chose the wrong encoding for the book (use windows-1252, not
iso-8859-1)

* the book itself encodes these characters incorrectly (some HTML books
have things like — despite the HTML spec saying numeric
character entities must be specified by their Unicode codepoints, and
Unicode U+0097 is a nonprintable control character)

In the first case it's easy to fix: pick the correct encoding.

In the second case you may have to edit the book to fix it.

Marius Gedminas
--
The moral of the story is that with a contrived example, you can prove
anything. Oops. No, that's not what I meant to say.
-- Joel Spolski

[Mike G.]

On Jul 2, 9:06 am, Marius Gedminas <mged...@b4net.lt> wrote:
> On Sun, Jul 01, 2007 at 11:51:42AM -0000, Mike G. wrote:
> > Some characters are showing up as boxed 0093 (in a box, 00 on top, 93
> > on bottom), 0094, or 0097.
>
> There are two possible reasons for this:
>
> * you chose the wrong encoding for the book (use windows-1252, not
> iso-8859-1)
>
> * the book itself encodes these characters incorrectly (some HTML books
> have things like &#x97; despite the HTML spec saying numeric
> character entities must be specified by their Unicode codepoints, and
> Unicode U+0097 is a nonprintable control character)
>
> In the first case it's easy to fix: pick the correct encoding.
>
> In the second case you may have to edit the book to fix it.

Marius,

Thanks for the info.

It appears that it's not the first situation -- none of the encoding
options
works around the problem.

I guess that leaves editing as a (painful) option.

Or not reading these broken books with FBReader, but that would be
sad.

Mike

[geometer]

Hi Mike,

> But the 0097 shows up on "Freehold" from the Baen free library at www.baen.com.

where in this book do you see '0097'? And which font do you use? (To
check font, go to the options dialog -> 'Styles' tab -> 'Family'
option.)

-- Nikolay Pultsin

[geometer]

> where in this book do you see '0097'? And which font do you use? (To
> check font, go to the options dialog -> 'Styles' tab -> 'Family'
> option.)

Ok, I've found '0097' in "Freehold". Mike, thank you for the report. I
will investigate the problem and fix it (if it is possible) before the
next FBReader version.

-- Nikolay Pultsin

[Mike G.]

geometer wrote:
> Ok, I've found '0097' in "Freehold". Mike, thank you for the report. I
> will investigate the problem and fix it (if it is possible) before the
> next FBReader version.

Thanks!

And thanks for the wonderful reader

[Mike G.]

On Jul 2, 4:21 pm, geometer <geome...@mawhrin.net> wrote:
> Ok, I've found '0097' in "Freehold". Mike, thank you for the report. I
> will investigate the problem and fix it (if it is possible) before the
> next FBReader version.

I've found a free story on Fictionwise that also demonstrates the
93/94 problem, http://www.fictionwise.com/eBooks/eBook31101.htm

Thanks again for investigating this.

[geometer]

Hi Mike,

good news: I've found and fixed '009x' problem. Fix will be available
in the next FBReader version (0.8.5).
I plan to release 0.8.5 in a few days. Thank you again for the report
and for the sample files.

-- Nikolay Pultsin

[Mike G.]

On Jul 5, 7:14 am, geometer <geome...@mawhrin.net> wrote:
> good news: I've found and fixed '009x' problem. Fix will be available
> in the next FBReader version (0.8.5).
> I plan to release 0.8.5 in a few days. Thank you again for the report
> and for the sample files.

Nikolay, thanks!!

Be careful, if you keep being this helpful, before you
know it everyone's going to be using this app :)