FBReader Release for the DR1000S

[wallcraft]

Originally Posted by godel10

In case I want to read a file format that the builtin reader of the device already reads (html, mobi) I am wondering what reader does people think it is better to use: the builtin one or fbreader?

On my iLiad, I always use FBReader because of:

font support
adjustable margins and line spacing
always bold option

Both readers fail to display the cover of recent MOBI ebooks. FBReader does not read DRMed MOBI.

On the iLiad, FBReader is slower to turn pages but there is more text per page (assuming narrower line spacing and smaller margins). Page turn speed should be more similar between the two on the DR.

A difference is that FBReader uses its own file navigation and library, but the library (since v0.8.16, i.e. on the DR but not on the iLiad) includes listing by tags - so it is much more flexible than file based navigators. See Book Tags in FBReader

FBReader does not do directory lookup on the DR, but it includes the "hooks" to do this via an external program (these currently only work on the Sharp Zaurus). It can select text, although there may be no default key binding for this on the DR (on a Desktop this is bound to <ctrl>-C, but like most things in FBReader this is customizable).

[Adam B.]

Originally Posted by godel10

In case I want to read a file format that the builtin reader of the device already reads (html, mobi) I am wondering what reader does people think it is better to use: the builtin one or fbreader?

I am concerning about issues like:
1. Comparing the battery consumption (anybody knows?)
2. As far as I have seen fbreader in the DR1000S does not support dictionaries, while the builtin one does.
3. What font makes easier the readeing in the fbreader program? On the other hand, in the buitin reader we cannot change the font (only the size).

But I am sure there are more drawbacks (of each of them) that I do not know about. Which ones?

It depends on what you need to do. HTML support should be better in FBReader, Mobipocket depends on the features you're looking for.

1. Battery life should be the same.
2. Correct.
3. Not sure. That's more likely a personal preference.

[allovertheglobe]

Originally Posted by godel10

In case I want to read a file format that the builtin reader of the device already reads (html, mobi) I am wondering what reader does people think it is better to use: the builtin one or fbreader?

I am concerning about issues like:
1. Comparing the battery consumption (anybody knows?)
2. As far as I have seen fbreader in the DR1000S does not support dictionaries, while the builtin one does.
3. What font makes easier the readeing in the fbreader program? On the other hand, in the buitin reader we cannot change the font (only the size).

But I am sure there are more drawbacks (of each of them) that I do not know about. Which ones?

Clearly FBReader for me for the formats supported by both, but let's not forget that FBReader also lets you read formats that would not be available otherwise.

1. Don't know, don't care: I bought the DR1000 for reading, not measuring battery life.
2. Nope, but the built-in one isn't exactly too useful in it's current implementation either...
3. As per point 1., I bought it for reading, and the FBReader offers one of the most important things in that regard: I can choose my font! That alone beats hands-down the built-in option, which only offers a sans-serif in various sizes.

While some people want even more specific font choices (install their own) FBReader already has a varied selection of both serif and sans-serif choices, plenty enough for me. Ludic reading for me means a serif font, it just flows better, and with the large screen and high resolution of the DR1000, it looks pretty good too (one of the reasons one usually switches to a sans-serif on a low-res display)

So right now I use Bitstream Vera Serif at 13pt (for some reason 12pt scaling is seriously ugly), with a 50 margin (*), 1.2 line spacing , justified. See an example below.

I just added a 2nd setting that I quite like: Century Schoolbook L at 13 pt, 50 margin, 1.0 line spacing, left (ragged right). See 2nd example below.

Always time display turned off, and full-screen.

(*) Checking things for this post, I finally figured out that margins DO work, but you have to use large numbers for a visible result, probably due to the high resolution.

Anyhow, FBReader is -free-, and nicely complements the DR1000 with functionality that it would not otherwise have, so there is no reason not to use it!!

[omro]

Pretty cool, I got this to work without any issues.

Can you customise the paragraph spacing?

[wallcraft]

Originally Posted by omro

Can you customise the paragraph spacing?

Look under the crossed tool icon, for Format -> Regular Paragraph.

[omro]

Thanks wallcraft!

OK, I'm very impressed with FB Reader. Well done Adam B. for the port, much appreciated.

The bundled fonts are horrid though, lol, though that's nitpicking. Is there anyway I can add fonts from my PC or is there anyway more fonts could be bundled? Arial or Tahoma or Palatino would be nice.

I also am assuming that access to the built in dictionary function is unlikely?

Is there any way FB Reader could open books from outside of the application? With the stylus calibration being so poor, I'm having a difficult time hitting the books and expanding and contracting the pluses/minuses in the library page.

[wallcraft]

Originally Posted by omro

The bundled fonts are horrid though, lol, though that's nitpicking. Is there anyway I can add fonts from my PC or is there anyway more fonts could be bundled? Arial or Tahoma or Palatino would be nice.

I also am assuming that access to the built in dictionary function is unlikely?

Is there any way FB Reader could open books from outside of the application? With the stylus calibration being so poor, I'm having a difficult time hitting the books and expanding and contracting the pluses/minuses in the library page.

So far as I know, no one has looked in detail at the DR font setup. The actual setup is typically defined in /etc/fonts/fonts.conf. If it is configured like the iLiad (i.e. like most Linux systems) user-supplied fonts can go in the directory ~/.fonts and the text file ~/.fonts.conf would define where else they can go (e.g. on the SD card). These files do not seem to exist. If more fonts were installed on the DR1000S, FBReader would be able to see and use them.

Access to the MOBI dictionaries is not available. However, some device-specific variants of FBReader do support dictionary lookup (so the needed "hooks" are there) and the existing DR1000S version should allow selecting text which might be manually exportable to the MOBI dictionary. I also wonder if a small DR1000S app could provide simple stand-alone access to the dictionary and eventually allow integration of the dictionary into FBReader.

See Updated Contentbrowser with FBReader support.

[omro]

Originally Posted by wallcraft

So far as I know, no one has looked in detail at the DR font setup. The actual setup is typically defined in /etc/fonts/fonts.conf. If it is configured like the iLiad (i.e. like most Linux systems) user-supplied fonts can go in the directory ~/.fonts and the text file ~/.fonts.conf would define where else they can go (e.g. on the SD card). These files do not seem to exist. If more fonts were installed on the DR1000S, FBReader would be able to see and use them.

Am guessing these files and directories are on the DR in places I can't get at, as I can't see them on the SD.

Originally Posted by wallcraft

See Updated Contentbrowser with FBReader support.

Thank you again wallcraft for the link, much appreciated and thank you again Adam B. for your hard work, it really is appreciated!

Another settings question. I've modified my margins, however modifying the bottom margin merely shifts the progress bar up, rather than preventing the text from almost colliding with it, which was my intent. Is there a setting to increase the separation between the bottom text and progress bar that I've not spotted?

Thanks again.

[wallcraft]

Originally Posted by omro

I've modified my margins, however modifying the bottom margin merely shifts the progress bar up, rather than preventing the text from almost colliding with it, which was my intent. Is there a setting to increase the separation between the bottom text and progress bar that I've not spotted?

As you say, the bottom margin is below the progress bar. To change the spacing above the progress bar, change "offset from text" under the "Indicator" tab. This tab can also change the width of the progress bar. Note that sometimes the space at the bottom of the text is large because this isn't enough room for another line of text.

[ec3008]

I've a problem to read a document with fbreader.
Could be that I miss something to do.
I'm tried to read chm and prc (not DRM). I use the icon with the book and plus sign, browse the dir, choose the file and the reader hung. I must reset to gain control.

Ther'is something that I miss, I must add a path in the options ?

thank for the help

Enrico

[wallcraft]

Originally Posted by ec3008

I'm tried to read chm and prc (not DRM). I use the icon with the book and plus sign, browse the dir, choose the file and the reader hung.

I don't have a DR1000S, but the book selection you describe sounds correct. Did you succeed with any ebook? I suggest trying HarryT's Dickens, Charles: A Tale of Two Cities (Illustrated). v3, 22 Mar 2008. This is a MOBI that should definitely work. Note that you don't get the cover image with FBReader, but there should be a navigable TOC.

If Tale of Two Cities works, then try reading your failing ebooks under FBReader on a Desktop PC (Windows, Linux, Intel Mac). Note that you can do this on the actual DR1000S files via USB.

Since FBReader copies a processed version of the entire ebook into main memory, very large CHMs can either take a long time to initialize or can hang the device. This should be less likely on the DR1000S than the iLiad, because it has more memory. On the iLiad "large" was above 5 MB, which unfortunately isn't all that large for a CHM. The only issue I am aware of with MOBIs is that "high" compression is not supported. In the Windows version of FBReader you get an error message about unsupported format if you try to open such a MOBI.

[pthwaite]

Wallcraft,
I have a problem with 2 books I have dedrmed. Both books work fine on both readers I have (Cybook & DR), but they won't open in FBreader, the Mac version doesn't display anything, the DR just shows garbage characters.

Could this be the high compression discussed above?

[wallcraft]

Originally Posted by pthwaite

Could this be the high compression discussed above?

Yes. A work around is to use Calibre's command line tool mobi2oeb, which explodes to an OEB ebook (HTML, images, and a .opf metafile). Sometimes you are better off deleting the resulting .opf file and just reading the .html directly in FBReader, but if the .opf works ok (open it in FBReader to check) then make a ZIP of the directory (give mobi2oeb a different directory for each ebook) and rename it .oebzip. This is treated as an OEB ebook by FBReader. To read the HTML, delete the .opf and make a ZIP of the directory. The ZIP can be opened by FBReader.

[ec3008]

Originally Posted by wallcraft

I don't have a DR1000S, but the book selection you describe sounds correct. Did you succeed with any ebook? I suggest trying HarryT's Dickens, Charles: A Tale of Two Cities (Illustrated). v3, 22 Mar 2008. This is a MOBI that should definitely work. Note that you don't get the cover image with FBReader, but there should be a navigable TOC.

If Tale of Two Cities works, then try reading your failing ebooks under FBReader on a Desktop PC (Windows, Linux, Intel Mac). Note that you can do this on the actual DR1000S files via USB.

Nothing to do.
I've loaded the mobi file but when I try to select it in the 'browse window' the reader hung.
another info, unlike the folder icon, the icon of the MOBI file appear greyed in the window.

Can someone give me a suggestion?
thanks
enrico

[Adam B.]

Try to select the library button when you open FBReader. Then, wait a few minutes (10 or more depending on how many files are on your SD card).

FBReader tries to automatically add supported files to the library. If you have a lot of files, it'll take a while to add.