PRS-T1 Future Firmware Request

[oscar11]

It would be great if PRS-T1 had an alphanumeric index bar, just like PRS-600.

[VelvetElvis]

The biggest thing I'd like to see is a way to turn off the dictionary. It seems about every 10th page turn or so, the ^$#@^ dictionary opens when I swipe to turn a page. As much as I'd hate to lose the dictionary, having it open unexpectedly is decidedly worse for me.

Better still, reserve double-tap for a dictionary lookup, and have a single tap for page turns, much like the Kobo page turns. I turn pages more often than I lookup words. ;-)

[bibahbuzemann]

Originally Posted by VelvetElvis

The biggest thing I'd like to see is a way to turn off the dictionary. It seems about every 10th page turn or so, the ^$#@^ dictionary opens when I swipe to turn a page. As much as I'd hate to lose the dictionary, having it open unexpectedly is decidedly worse for me.

Better still, reserve double-tap for a dictionary lookup, and have a single tap for page turns, much like the Kobo page turns. I turn pages more often than I lookup words. ;-)

Wow. The Kobo does seem to be the better eReader(and I agree). But I love the T1. Just try to pry it out of me cold, dead hands.

[Tinderbox (UK)]

1 : First page after waking up the T1, is very faint and hard to read, especially if you use a small font, can they fix this.

2 : The ability to change the line spacings.

Sorry if this has been mentioned.

John.

[JSWolf]

Originally Posted by susaz

I´d love to have the time, date, batt info and name of the book on top of the screen as the Bq Avant

I'd be happy with just the battery info on he bottom of the screen when reading a book. Also, as part of the menu while reading the book, I'd like the option to delete it.

The time should also be able to fit at the bottom. But if you want the name at the top, make it optional as I don't want to give up the extra screen space for it.

[JSWolf]

Originally Posted by ghostyjack

While they are at it, it would be nice to actually have true italics - not just slanted text.

Originally Posted by chrisridd

I generally use the Amasis font which has proper italics. When the Reader decides to show them, anyway

Originally Posted by Bear 100

For a dedicated e-reader, the font issue is disappointing. I expect, just like in a book, sharp clear fonts, justified, and true italics. I certainly like the ability to increase font size, but expect that they be displayed properly.

If you go to the following link, you can get a modified reader app for the T1 that fixes the bugs when switching fonts. IT adds a few more features like customizing the font menu. You do not have to have your T1 rooted for this to work.

https://www.mobileread.com/forums/sho...09#post1931909

[JSWolf]

Originally Posted by bibahbuzemann

Wow. The Kobo does seem to be the better eReader(and I agree). But I love the T1. Just try to pry it out of me cold, dead hands.

I cannot and will not ever recommend a Kobo reader to anyone unless they get off their lazy asses and fix the embedded font bug. It's a fix that needs to be made and it hasn't. The T1 has been hacked to fix it's biggest bug and it's an easy install.

[JSWolf]

Originally Posted by Tinderbox (UK)

1 : First page after waking up the T1, is very faint and hard to read, especially if you use a small font, can they fix this.

2 : The ability to change the line spacings.

Sorry if this has been mentioned.

John.

Changing the margins would also be nice.

[jackie_w]

Originally Posted by JSWolf

Changing the margins would also be nice.

Can't you use the custom CSS feature in Morkl's modified reader app (as per your ref in post #21) to do this? I just tried it on mine. Seems to work OK.

[JSWolf]

Originally Posted by jackie_w

Can't you use the custom CSS feature in Morkl's modified reader app (as per your ref in post #21) to do this? I just tried it on mine. Seems to work OK.

You can try. But some eBooks have a page-template, some use @page, and some have margins not in the body style. So yes you can do it on some and not others.

The solution is to take a look at the ePub and see if it page a page-template. That I always remove. There's no need for it. @page I always remove. If you get rid of the page-template and any @page, you might be able to have your own style handle the margins as you want.

[jackie_w]

Originally Posted by JSWolf

You can try. But some eBooks have a page-template, some use @page, and some have margins not in the body style. So yes you can do it on some and not others

I think you can override an @page in the epub with your own @page in the custom css.

Edit: There's a caveat on using a custom @page, though. If you use any settings other than zero, your page 1 cover will probably look a bit odd.

[JSWolf]

Originally Posted by jackie_w

I think you can override an @page in the epub with your own @page in the custom css.

But you can't override a page-template. You have to delete them and then remove the reference in the OPF and in all the XML that have such.

@page {
  margin-top: 0;
  margin-bottom: 0;
  margin-left: 0;
  margin-right: 0
{
body {
  widows: 0;
  orphans: 0;
  margin-top: 0;
  margin-bottom: 0;
  margin-left: 0;
  margin-right: 0;
  text-align: justify
}

There you go. That will do if it works.

[jackie_w]

Originally Posted by JSWolf

But you can't override a page-template.

I didn't say you could.

Originally Posted by JSWolf

You have to delete them and then remove the reference in the OPF and in all the XML that have such.

For anyone interested, a Calibre epub-to-epub conversion will remove all page-template.xpgt margins automatically. Or if you don't want to convert epub-to-epub, there's a Calibre 'Modify epub' plugin that will remove them too, and do lots of other things besides.

[JSWolf]

Originally Posted by jackie_w

For anyone interested, a Calibre epub-to-epub conversion will remove all page-template.xpgt margins automatically. Or if you don't want to convert epub-to-epub, there's a Calibre 'Modify epub' plugin that will remove them too, and lots of other things besides.

For anyone interested, DON'T do an ePub > ePub conversion. Load it into Sigil and edit it.

[ChesserCat]

I'm thinking more about the .PDF reader aspect of the device. I have tons of .PDF files. I've only recently started collecting ePubs.

In crop mode, it only lets me select one screen area for the whole page. In some of my files, the type is sufficiently small and the page sufficiently big that I have to turn the device landscape to get the text large enough to read, in addition to killing the margins. I can't use crop mode on them, because they will only show me the top section of the page (not quite half of the page, in many cases). If I turn landscape on a page with portait dimensions, I need the ability to mark 2 or 3 different cropped sections on the page. They may have some overlap. Forward and back buttons should iterate through those different sections before moving to the next/prior page.

In page mode, I can stretch the image, zooming in enough that the text becomes readable. I can drag the left, right, up or down to see all the page (works better on an LCD than eInk, but that's just a shortcoming of eInk tech). That's reasonable. I can't drag my way onto the next or previous page (that I'm aware of; feel free to correct me if I just haven't figured this out). The only way I know of to get to the next page is to use the forward button. When it gets to the next page, it loses my zoomed settings. Ideally, if I zoom in and move to another page, it should remember my zoom settings and my offset from the top left corner. Even better, if the even and odd pages have slightly different margins on them, it should allow me to adjust the offset for each and have it remember them from one page to the next.

For some of my files, the rendering is painfully slow. Ideally, when I open a .PDF, it would render and display the current page, then render (in the background) and cache the prior page and the next page. Then, when I hit forward, it would take me to the pre-rendered image of the next page, very quickly, and start rendering the following page in the background. If it only holds 3 pages in memory at any given time, that should keep the memory requirements down but still allow it to move from one page to the next (typical reading pattern) with very little delay. I had a PDF reader which I used on my old Tapwave Zodiac which did this, and it was very speedy (with a much slower processor).

That last idea might be one for the ePub reader, too. It's hard to stay engrossed in what you're reading if you can't "flow" smoothly from one page to the next.