I'll be setting up an installer for FBReader with 2.11 when it's released. My question is, what file extensions should should be opened with FBReader from the contentlister?

According to fbreader's website it supports:

# Supported formats are

* 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.
* .epub

PDB, TXT, HTML are already supported natively so the list should include



chm
rtf
oeb
opf
epub
fb2
tcr?


Let me know if there are any additions or corrections. I don't use FBReader for much other than chm, so the rest is up to you guys!

LIT would be nice. :)

LIT would be nice. :)

In this thread, I'm talking about file types that are already supported by the FBReader program. This is mostly for the people who are manually adding files to the FBReader library.

However, since I have convertlit compile for the iLiad, I can script something that will automatically remove the drm and convert to oeb format and open in FBReader...

But let's keep this thread on track. :smash: :)

I don't know about other folks, but I'd rather (by far) read HTML and TXT in fbreader than in the viewer provided on the iLiad. So a script that lets me make that adjustment would be greatly appreciated.

(I'd also like to throw in another vote in favor of the auto-LIT-convert script you described.)

I really wish we could get an adjustable number of items in the Contentlister page....

OEB documents are often held in a zip bundle, and FBReader recognizes the extension .oebzip for this kind of document. Several of these file formats typically have the extension .pdb (Plucker, Palmdoc, zTxt), but so do many other kinds of files - including some e-book formats. This sometimes causes confusion, but it may be better to map .pdb to FBReader than to nothing. Or explicitly check bytes 61-68 for the strings: "DataPlkr", "TEXtREAd" (Aportis Doc), or "zTXTGPlm".

Hmmm all fbreader extensions except the ones that the Iliad supports native. But you could then add an option asking if html and txt are also runnable from content reader.
On the other hand, if I wanted fbreader to read a txt instead of the iliad, I just add it to the fbreader library...

I too read html files with FBReader.