This is the first installer for FBReader running on the DR1000S.

For those who aren't familiar with FBReader, it's an ebook reading software with a built in library and support for many formats.

Supported formats are:

ePub format
fb2 e-book format (style attributes are not supported yet).
HTML format (tables are not supported).
CHM format (tables are not supported).
plucker format (tables are not supported).
Palmdoc (aportis doc).
zTxt (Weasel format).
TCR (psion text) format.
RTF format (stylesheets and tables are not supported).
OEB format (css and tables are not supported).
OpenReader format (css and tables are not supported).
Non-DRM'ed mobipocket format (tables are not supported).
Plain text format.


To read a book, you'll have to add it to the library. You can do this by clicking the icon that looks like a book with a "+" sign.

You'll also need to close out of the program by clicking the exit button in the upper right. I plan to support the menu eventually, but I have to dig into that further.

To install: Unzip the file to the root of your SD card. For example, if your SD card shows up as the E:\ drive on your computer, you should have an E:\Programs folder after you unzip it.

After installing, you'll be able to select the FBReader icon from the Documents/Programs folder on your device.

You can toggle full screen mode with the select button (between up and down).

You can find more information about FBReader at their website (http://fbreader.org/about.php).

It was actually *very* easy to port, since the DR1000 has a lot of libraries already built for it. Screen refreshes are *fast*. The internal refreshes are amazingly accurate. It only refreshes what's changed on the screen. I didn't have to build in any refreshes into FBReader itself. All of the built in menus and library functions work perfectly.

It's hard to describe how amazingly easy this was in comparison to iLiad ports.

Thank you iRex for making a device that *very* easy to hack on (and for providing the device for my "review")! :thanks: :2thumbsup

If you would like to open supported files directly from the Content Browser, see this thread (http://www.mobileread.com/forums/showthread.php?t=31920).

Wow, that was fast. Looks tickety boo :) I look forward to trying it.

regards

Adam, you've answered another question of mine indirectly :) Care to point towards a few resources for the basics? I'd like to play around with the source etc.
What kind of development environment do you use? Your setup, tools, etc.

Kind regards
Seref

Adam, you've answered another question of mine indirectly :) Care to point towards a few resources for the basics? I'd like to play around with the source etc.
What kind of development environment do you use? Your setup, tools, etc.

Kind regards
Seref

I plan on setting up a post explaining how to setup a development area. I did all of this with the iRex provided SDK on Ubuntu Linux.

Hell, that is great ... my favorite program for the Iliad ... please don't remove the buttons (like someone tried with the Iliad FBReader ...)

Hell, that is great ... my favorite program for the Iliad ... please don't remove the buttons (like someone tried with the Iliad FBReader ...)

That someone was me ;)

It was done to speed up page turns. That won't be necessary on the DR since all refreshes are done internally.

This is the first installer for FBReader running on the DR1000S The screenshots look very nice. Did you also port a screenshot program to the DR?

The screenshots look very nice. Did you also port a screenshot program to the DR?

I made those running fbshot in the SDK, so they're not exactly "true" screenshots. Fbshot will run on the DR, but I have to set up a delay script.

THANKS Adam!!!!!

ehm Adam I have a simple request ... can you port a djvu viewer? :D :D

can you port a djvu viewer? The issue on the iLiad was the lack of Qt library support, because almost all X11 djvu viewers use Qt. The only GTK+ djvu viewer I am aware of is evince, and if Qt still isn't possible on DR perhaps evince makes sense (even though it isn't needed for PDF). There is a version of evince for the Nokia tablets, so if can run on relatively resource-poor devices.

:thanks:

Wow, that was fast.

After some experimentation:
It's OK to move the FBReader.desktop to the /System/Desktop/ folder.
It's not OK to modify it:
- changing the path to /System/Programs/ doesn't work, the shortcut works, but then the reader hangs... (after moving Programs there first, of course) I guess some paths are hardwired?
(I would prefer to have all the software in /System, and use the root only for content)
Interestingly, it also seems you have to use the rather more cryptic /media/mmcblk0p1/ than the usual ../Programs for System/Programs or ../../Programs for FBReader's default location

One bug I ran into when setting up my library path using the software keyboard: I used the TAB key to see if it would auto-complete, but all it did was auto-destruct: the screen refresh went berserk, and after a while I managed to cancel the entry, but re-doing it immediately went back to the screen-refresh cycle, and finally the reader hung when trying to quit.

Now that may well be a bug with the software keyboard... (which could use some contrast adjustment too) Oh, and a file selector would be nice. (Since I'm lazy ;) which is why I tried the auto-complete in the first place)

For some reason, the popup selectors (ex. Font Family, Line Spacing) pop up and disappear almost instantly, so one has to be very fast. EDIT: OK, keep holding down, don't tap... still a bit fiddly. But finally not just one but several SERIF fonts - YES!

Margins (set in Options) seem to get ignored, at least in .epub.

P.S.: Is there a way to modify the .desktop properties so the shortcut-arrow overlay doesn't appear, like iRex's own icons?

This is nitpicking of course. FBReader works already very well (at least with the .epub books I tried)

Congratulations Adam for getting this working so soon!

I got some problems reading some .CHM files in FBReader ( Same on iliad 2). Some characters doesn't show up properly. Is there a way I can change the font type or something? For example the file contains a character '-' but on FBR it shows some digits in a small square

I got some problems reading some .CHM files in FBReader ( Same on iliad 2). Some characters doesn't show up properly. Is there a way I can change the font type or something? For example the file contains a character '-' but on FBR it shows some digits in a small square
That means it can't display that character so it replaces it with the corrsponding code. Typical Linux.

Try changing the encoding in the FBReader options under "Language". As a last resort try changing the font family (unlikely though)

Adam, you rock. Thank you for this.
Probably one of iRexs smarter moves to hand out a DR1000S review unit to you ;-).

:thanks:

Wow, that was fast.

After some experimentation:
It's OK to move the FBReader.desktop to the /System/Desktop/ folder.
It's not OK to modify it:
- changing the path to /System/Programs/ doesn't work, the shortcut works, but then the reader hangs... (after moving Programs there first, of course) I guess some paths are hardwired?
(I would prefer to have all the software in /System, and use the root only for content)
Interestingly, it also seems you have to use the rather more cryptic /media/mmcblk0p1/ than the usual ../Programs for System/Programs or ../../Programs for FBReader's default location



/Programs is where I compiled it to run from. I could have just as easily used /System, but I figured Programs was a good compromise for hiding the data files, as well as a place to browse to all 3rd party programs. It's path is hard coded, but it does have to be put where I compile it for. The shortcut can be put anywhere. iRex has plans to make shortcuts use relative paths instead of the full location, but it's not implemented yet.


One bug I ran into when setting up my library path using the software keyboard: I used the TAB key to see if it would auto-complete, but all it did was auto-destruct: the screen refresh went berserk, and after a while I managed to cancel the entry, but re-doing it immediately went back to the screen-refresh cycle, and finally the reader hung when trying to quit.

Now that may well be a bug with the software keyboard... (which could use some contrast adjustment too) Oh, and a file selector would be nice. (Since I'm lazy ;) which is why I tried the auto-complete in the first place)

There's a file selector when you click on the "Add Book" icon. (Book with a plus sign) You should be able to browse the memory card and find whatever you want to add to the library.



For some reason, the popup selectors (ex. Font Family, Line Spacing) pop up and disappear almost instantly, so one has to be very fast. EDIT: OK, keep holding down, don't tap... still a bit fiddly. But finally not just one but several SERIF fonts - YES!

I've found it's easiest to click on the box, and use the up and down arrows to navigate. It is a bit funky though.


Margins (set in Options) seem to get ignored, at least in .epub.

Looks like an FBReader bug.

P.S.: Is there a way to modify the .desktop properties so the shortcut-arrow overlay doesn't appear, like iRex's own icons?

Not sure yet. I've just scratched the surface of the the DR can do. :thumbsup:

This is nitpicking of course. FBReader works already very well (at least with the .epub books I tried)

Congratulations Adam for getting this working so soon!

It wasn't as difficult as I thought it would be. iRex has really done a lot of things right this time around.

That means it can't display that character so it replaces it with the corrsponding code. Typical Linux.

Try changing the encoding in the FBReader options under "Language". As a last resort try changing the font family (unlikely though) The encoding is "per book", so it is under the Book Info (lamp bulb) icon. The problem is often ISO-8859-1 encoding instead of Windows-1252, however an ePub should have the encoding listed in the file. There is a language tab under the options (tools) icon to set the default encoding.

The other possibility is a font with missing characters. The best coverage under Linux is typically from DejaVu Sans. This is set under the Styles tab (Options). When I get this problem, I typically first set the font to DejaVu Sans and they I play with the encoding. Once you have the right encoding, try your favorite fonts.

Nice. It works fast with chm files. :thanks:

/Programs is where I compiled it to run from. I could have just as easily used /System, but I figured Programs was a good compromise for hiding the data files, as well as a place to browse to all 3rd party programs. It's path is hard coded, but it does have to be put where I compile it for. The shortcut can be put anywhere. iRex has plans to make shortcuts use relative paths instead of the full location, but it's not implemented yet.
I see. To clarify, I was thinking /System/Programs/, but your choice is fine. It's interesting though that the location of the program is depended on the compilation, rather than being self-contained/independent and just linking to the (system) libraries.

There's a file selector when you click on the "Add Book" icon. (Book with a plus sign) You should be able to browse the memory card and find whatever you want to add to the library.
Aha, so it's only when you set the default path in Options that you have to manually enter it.

I've found it's easiest to click on the box, and use the up and down arrows to navigate. It is a bit funky though.
Thanks for the tip, that helps.

The encoding is "per book", so it is under the Book Info (lamp bulb) icon.
I'm quite new to FBReader, didn't realize you had a -per book- setting on top of the general "Options" setting. Good to know.

I see. To clarify, I was thinking /System/Programs/, but your choice is fine. It's interesting though that the location of the program is depended on the compilation, rather than being self-contained/independent and just linking to the (system) libraries.

The libraries aren't the problem, it's the resources (icons, config, etc) that needs a static location.

The libraries aren't the problem, it's the resources (icons, config, etc) that needs a static location.
Is that because it doesn't use the standard folders (.config, /usr/share/icons or similar, etc) because it isn't really "installed" but rather self-contained?

A couple more observations using the various option windows and file requesters:
- Plain text: margins are still ignored (still my new default text viewer!)
- Copy & paste works, nice! (ctrl-C, ctrl-V, ctrl-X) (Tab-completing doesn't, careful!)
- Finally a glimpse behind the scene (the actual OS filesystem)

Which leads to my next request: Any chance for a Terminal application? It would be handy, if only to rename documents, create subfolders etc. since none of that is supported in the current interface. Generally provide a little more independence from having to connect the reader or pop the card out to do the above. Yes, it can be dangerous, but hey it'd be only for people who like living on the edge :cool:

And of course the reason I have always been jealous of Iliad owners, being an old school gamer: GARGOYLE :2thumbsup or any IF VM (Frotz...)
(I am embarrassed, after searching around a bit, to find out I already asked for it on the Iliad, even though I never got one... some things don't change... Oh and I like the Iliad software keyboard design much better)

Which leads to my next request: Any chance for a Terminal application? If most of the screen refresh stuff is in the GTK+ library, then Xfce-Terminal (http://www.os-cillation.com/index.php?id=42&L=5) may be a good candidate. It is the basis for osso-xterm (http://770.fs-security.com/xterm/) for the Nokia tablets.

This is the first installer for FBReader running on the DR1000S.

Adam,

Is there any magic directory on the card where I can put my own fonts?
Otherwise it works really nice - basically same as on Nokia tablets.

Thank you,

Leonid

Thanks you so much, it is brilliant. I haven't expected it for a half year...

Adam,

Is there any magic directory on the card where I can put my own fonts?
Otherwise it works really nice - basically same as on Nokia tablets.

Thank you,

Leonid

Unfortunately not. The only way to get new fonts on the reader is to copy them to the root partition and update the font config. It's possible with some Linux knowledge, but not easy for the average person.

Unfortunately not. The only way to get new fonts on the reader is to copy them to the root partition and update the font config. It's possible with some Linux knowledge, but not easy for the average person.
Ok, so I assume that your build of FBReader doesn't have a functionality to load fonts from location other than system one (like e.g. build for Jinke V3 devices is doing).
It's not a problem for me to copy files from sd to root partition using command line and edit font config file - but is it possible to use command line on the device itself - or is the only way to install sdk and do it remotely?

Thank you,

Leonid

Nice work. I have one question though, in CHM files how do I go to the next section?

Probably the best way is to map the Long down button keypress to the "Next TOC Section" in the options.

I've setup a new options file that does this for you. Copy the attached file to x:\Programs\.FBReader\ and overwrite the existing file.

The next time you open FBReader, you should be able to do a long keypress on the down or up buttons to go to the next and previous sections.

It's not a problem for me to copy files from sd to root partition using command line and edit font config file - but is it possible to use command line on the device itself - or is the only way to install sdk and do it remotely?

That is - is there a chance to see a DR1000 version of Xshell any time soon?

That is - is there a chance to see a DR1000 version of Xshell any time soon?

The problem with getting a shell on the DR, is that the internal refreshes rely on the GTK expose event. All of the shells that I have tried do not call that event, so screen refreshes don't work correctly.

I am new to the DR1000s and to FBreader, so perhaps I'm just doing something wrong, but i can't get Fbreader to work at all.

I extracted the entire contents of the zip to root level "Programs" folder on the DR1000 device. When I then use the device, I see the Programs folder containing all the files under "Documents".

I only see one file with a icon other than the many PNG files; There is an "FBReader with a "four leaf" icon with an arrow I take to be a shortcut type of thing. But when I click on this with the stylus, the screen refreshed twice and nothing else happens. No reader opens. I am running software build 1.01 on my 1000s.

Thanks.

I am new to the DR1000s and to FBreader, so perhaps I'm just doing something wrong, but i can't get Fbreader to work at all.

I extracted the entire contents of the zip to root level "Programs" folder on the DR1000 device. When I then use the device, I see the Programs folder containing all the files under "Documents".

I only see one file with a icon other than the many PNG files; There is an "FBReader with a "four leaf" icon with an arrow I take to be a shortcut type of thing. But when I click on this with the stylus, the screen refreshed twice and nothing else happens. No reader opens. I am running software build 1.01 on my 1000s.

Thanks.

On the DR, you shouldn't see any PNG files. Only the icon should appear. Try to download and extract it again. If that doesn't work, try extracting with a different program (7zip or winzip for example).

Hmm, maybe you decompressed the folder or copied the contents over the wrong way somehow. On a computer, you should see an "_fbreader" folder (and perhaps metadata.db) inside of "Programs" on the root of your SD card.

On the DR1000, the "Programs" folder should appear to be empty other than the shortcut, PNG files or anything. Because the paths are hard-coded, the location and folder names need to be *exactly* like that.

For me, it worked without a problem. As a matter of fact, I moved the FBReader shortcut ONLY into /System/Desktop so it appears right away in the Home when I turn on the reader.

(Oops, looks like Adam beat me... slow wordy typist that I am -_-;)

Probably a silly question, however, When you "moved the shortcut" did you just drag & drop it on the PC? I tried to create a shortcut to the shortcut & that went belly up.

Probably a silly question, however, When you "moved the shortcut" did you just drag & drop it on the PC? I tried to create a shortcut to the shortcut & that went belly up.

You can do it on the PC. Just copy and paste it anywhere you like.

Thank you, Howard

To clarify further: the shortcuts on your reader are Linux-style shortcuts (ending in .desktop), which is why you have to drag & drop the shortcut file itself (as you mentioned) or copy & paste it (like Adam mentioned)

If you create the usual Windows/Mac-style shortcut, the reader won't know what to do with those.

Thanks, I had already sussed out the shortcut names but was just checking I didn't have to create/make a new one to point to somewhere else. I have moved them now & just need to reboot & try it :)

Thanks again.

mis posted.

So thanks to everyone responsible for FBreader and for porting it to the DR. One thing though, on the FBreader documentation page, there really ought to be a picture of the icon bar with labels showing what each does. Many are described on that page--many are not.

Mostly I have had good luck with this on the DR with one issue--I cannot use it with the stylus turned off. Without the stylus, I can turn pages, but that's it. When I get to the end of a section, I cannot go to the next section, close the book or do anything but back up really by using the buttons.

Also, and this is not a big deal and is probably asking a lot, but a zoom feature would be great. Of course, arguably the device should provide that (like the Ipod-touch does yeah!). Documents containing graphics can be difficult to make out. But hey, it's a gigantic boost to usability for the DR, so thanks all!

For a solution for the next section issue, see this post (http://www.mobileread.com/forums/showpost.php?p=281115&postcount=28).

I do plan to eventually move all the icons into the DR's menu system, but I have to do more research and spend a lot more time with it. FBReader was really just a good starting point for the first DR port.

One thing though, on the FBreader documentation page, there really ought to be a picture of the icon bar with labels showing what each does. Many are described on that page--many are not.
See Visual Tour of FBReader on a Pepper Pad 3 (http://www.fbreader.org/alan/). Some of this is out of date, but the Pepper Pad 3 also uses the standard Linux Desktop version of FBReader (like the DR1000).

Mostly I have had good luck with this on the DR with one issue--I cannot use it with the stylus turned off. Without the stylus, I can turn pages, but that's it. When I get to the end of a section, I cannot go to the next section, close the book or do anything but back up really by using the buttons. It is possible to map "actions" to keys (Keys tab under the crossed tools icon). I don't know if the DR1000S has long and short key presses and if it distinguishes between the two up/down clusters, but you can experiment under the keys tab to see how many key options you have and take a look at the available actions.

Also, and this is not a big deal and is probably asking a lot, but a zoom feature would be great. ... Documents containing graphics can be difficult to make out. Graphic support is very basic in FBReader. Currently, Image Scaling is in the plans for "versions 0.9.*".

I got it to work. Very cool!

How hard would it be to port evince-gtk?
I'd really like to get a djvu reader....

Maybe I'll try.

I got it to work. Very cool!

How hard would it be to port evince-gtk?
I'd really like to get a djvu reader....

Maybe I'll try.

It doesn't appear to be to difficult to port. I have it running in the emulator.

Now getting it to work with the right file formats is a different issue...

Where does FBReader store its preferences & library information (beyond the actual book files)? I browsed the SD card, admittedly casually, but couldn't identify anything like .something file, maybe I missed it...

Where does FBReader store its preferences & library information (beyond the actual book files)?
From post #28:

x:\Programs\.FBReader\

It doesn't appear to be to difficult to port. I have it running in the emulator.

Amazing! Cool!!

Now getting it to work with the right file formats is a different issue...

I thought of two solutions (well, maybe hacks...)

First, the ugly one is a script that creates an additional .desktop file for the files you'd like to read, that will then call the program with the right argument. Kind of like starting FBReader, but instead starting it already with the argument saying which file it should display. That would certainly work, and would certainly be ugly. The best would be probably to have all the .desktop files in a different directory than the files so you don't see everything twice.

The second option which I'm not sure will work is to write a plugin for iRex's viewer shell that can start a script when called. But I don't know if this is possible or feasible.

But the first should be easy.
I did this:
One file called Animals.desktop, containing
[Desktop Entry]
Encoding=UTF-8
Name=Animals
Comment=E-book reader
Exec=/media/mmcblk0p1/Programs/_fbreader/bin/fbreader2
Type=Application
Icon=/media/mmcblk0p1/Programs/_fbreader/share/pixmaps/FBReader.png


And a script called Programs/_fbreader/bin/fbreader2

Containing:
#!/bin/sh

/media/mmcblk0p1/Programs/_fbreader/bin/FBReader /media/mmcblk0p1/Documents/animals.html

Ugly, but it works. It would be easy to make a script that runs over your disk and creates these files automatically....

Did anyone manage to follow a link from one html file to another in FBReader?

I tried putting relative path, absolute path in the html file, nothing seems to work...

I have a strange problem...

It seems once I quite FBReader, I can't start it again. I have to reboot the DR.
I'm not sure if it happens always, but it surely happens often.

A second problem is that sometimes it takes a veeeery loooong time from the time I clicked on an html file in the file dialog till the dialog that asks me for the author etc. comes up. Does anyone know why that is? What is FBReader doing during that time?

I have a strange problem...

It seems once I quite FBReader, I can't start it again. I have to reboot the DR.
I'm not sure if it happens always, but it surely happens often.

Have you modified the launcher to start with a shell script? This is a problem with scripts and the current content browser.


A second problem is that sometimes it takes a veeeery loooong time from the time I clicked on an html file in the file dialog till the dialog that asks me for the author etc. comes up. Does anyone know why that is? What is FBReader doing during that time?

Do you have a lot of supported files on your memory card? FBReader could be scanning those to add to the library. You should try going into options, and removing the option to automatically scan your library for files.

Did anyone manage to follow a link from one html file to another in FBReader? This isn't possible, since FBReader only supports single-file HTML ebooks. If you have multiple related HTML files (e.g. book chapters) then you need to make an OEB ebook by adding a .opf file (which lists the HTML files among other things), zipping all the related files into one .zip and finally rename it .oebzip. Then links between HTML files in the OEB ebook will work. If you don't want to make an .oebzip, point FBReader to the .opf file for the same effect.

FBReader's ePub capability is a work in progress (it ignores the Table of Contents for example), but if you already have an internal TOC (or any base HTML file that eventually links to all the others) then Calibre on a Desktop PC (Windows, Mac, or Linux) is a good way to get from multiple HTMLs to an ebook. Use it to make an ePub by providing it with the base HTML file (via any2epub on the command line, or select ePub as your desired export target in the GUI).

Note that FBReader can follow external HTML links by invoking a web browser, this does not help on the DR1000S since it has no browser yet.

From post #28:
x:\Programs\.FBReader\
DOH. Forgot to "Show Hidden Files"... been a bit distracted by some $^@#& identity theft issues...

This isn't possible, since FBReader only supports single-file HTML ebooks. If you have multiple related HTML files (e.g. book chapters) then you need to make an OEB ebook by adding a .opf file (which lists the HTML files among other things), zipping all the related files into one .zip and finally rename it .oebzip. Then links between HTML files in the OEB ebook will work. If you don't want to make an .oebzip, point FBReader to the .opf file for the same effect.


Thank you! That was any amazingly detailed post.
In the end I had to do two more steps, I think because of teh format of my html files.

First I used html2oeb to build the opf file, then I had to change all href="content/, by removing 'content/' in the opf file. Then I moved the opf to the content directory, and then I zipped it all up and renamed it oebzip.

But after all that it worked!

:)

For those who aren't familiar with FBReader, it's an ebook reading software with a built in library and support for many formats.

Is there any advange of FBReader if I just want to read pdf files?

Adi

Is there any advange of FBReader if I just want to read pdf files?
Nope, but it does make it possible to read a whole bunch of formats that the DR1000 doesn't officially support (yet). Visit the official page (http://www.fbreader.org/) for more info.

So yesterday I settled down for a couple of hours of quality reading time. I started off in FBReader, then switched over to a PDF.

FBReader seems to have this refresh issue (?) where it will refresh every ~60sec or so even if you don't do anything (i.e. just read the page), but that can perhaps not be avoided even if it is somewhat distracting.

However, it carries over on the rest of the reader software as well, so even when reading a PDF, I was getting the same refresh flashes.

And when I switched back to FBReader and opened the options window, everything went haywire once the virtual keyboard came up, flashing back and forth, off and on until after a couple of minutes I had to do a reset...

So for now, I would advise people to only use FBReader by itself, and close it when you're done, rather than switch back and forth.

FBReader seems to have this refresh issue (?) where it will refresh every ~60sec or so even if you don't do anything (i.e. just read the page), but that can perhaps not be avoided even if it is somewhat distracting. Do you have time showing on the indicator bar? If so, try turning this off (crossed-tools -> Indicator -> Show Time).

Do you have time showing on the indicator bar? If so, try turning this off (crossed-tools -> Indicator -> Show Time).
Indeed. Thanks, that took care of it.

I guess this goes right back to the issues that came up when people in the iRex forum requested a clock to be put on the toolbar (even though that could maybe taken care of by doing a local refresh by the system rather than a fullscreen one by a generic app like FBReader?)

even though that could maybe taken care of by doing a local refresh by the system rather than a fullscreen one by a generic app like FBReader? FBReader should do a local refresh too, but probably the developers did not have EInk on their radar. An alternative, which might be easy to implement in FBReader, would be to only update the time when turning a page.

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?

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 (http://www.fbreader.org/docs/tags.php)

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).

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.

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!!

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

Can you customise the paragraph spacing?

Can you customise the paragraph spacing? Look under the crossed tool icon, for Format -> Regular Paragraph.

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.

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 (http://www.mobileread.com/forums/showthread.php?t=31920).

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.

See Updated Contentbrowser with FBReader support (http://www.mobileread.com/forums/showthread.php?t=31920).

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.

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.

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

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 (http://www.mobileread.com/forums/showthread.php?t=17594). 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 (http://www.fbreader.org/) 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.

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?

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.

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 (http://www.mobileread.com/forums/showthread.php?t=17594). 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 (http://www.fbreader.org/) 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

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.

FBReader tries to automatically add supported files to the library. If you have a lot of files, it'll take a while to add. Supported files include .prc (MOBI), but not CHM. If you don't want these files to be automatically added, edit your book path (General Tab under crossed tools icon). You can always manually add ebooks using the BOOK+ icon.

Ok.
all works now.
I only had to wait that browse my library (very huge)
Now works fine
thanks
Enrico