Sony T-2 ereader

[Dulin's Books]

Nate over at the Digital Reader foud a new Sony Reader sneaking through the FCC http://www.the-digital-reader.com/20.../#.T_RXNvUgvgo

[Phogg]

The thing this doesn't hint about is whether or not the crap software from the T1 is replaced.

The alphabetic tab navigation in all previous Sony readers was a feature of primary importance for those of us who carry around large libraries.

[MikeB1972]

Ah good, been waiting for this, they normally bring out a new reader in september.

I'm hoping Sony stick to their usual flow of release a new product, release a good product, change everything, rinse & repeat.
PRS-500 -> PRS-505
PRS-600 -> PRS-650
PRS-T1 -> Hopefully a T1 equivalent with all the rough edges smoothed out.

[talaivan]

It would seem almost certain they're going to use Android, as they did in the T1. If they upgrade the software for the T2, just maybe they'll issue an update to the T1 with the same upgrade. But, sadly, probably not -- since they won't be making money with the T1 anymore.

[Phogg]

Originally Posted by talaivan

It would seem almost certain they're going to use Android, as they did in the T1. If they upgrade the software for the T2, just maybe they'll issue an update to the T1 with the same upgrade. But, sadly, probably not -- since they won't be making money with the T1 anymore.

Alphabetic tabs are possible with android. Switching to android did not necessitate dropping to bare bones search functionality.

[rkomar]

Originally Posted by Phogg

Alphabetic tabs are possible with android. Switching to android did not necessitate dropping to bare bones search functionality.

It's not quite bare bones. If you tap on the "Page X of Y" at the bottom of the display, you get a slider that you can use to jump to a particular page number. Hold your pen on the slider bar and drag it around; you can see the name of the first book on the page the silder is pointing to without jumping there until you lift the pen. I prefer it to the alphabetic tabs now that I'm used to it because its faster.

[Quexos]

Can't wait to hear officially from Sony. Hope this one is a real improvement over the previous one.

[jackie_w]

For anyone who isn't satisfied with the reading experience on the PRST1, you could consider installing Morkl's modified reader app. It installs easily on both non-rooted and rooted devices which are using the latest Sony firmware v1.0.04.12210:

• custom fonts now work properly, i.e bold & italics no longer disappear when setting font to anything other than 'Original'
• can customise all 7 fonts (Original plus the 6 select-a-font) to your personal favourites
• fine control over font-sizes - choose your own 8 sizes
• control number of pages between each full page refresh
• option to make clock visible from within each book

Nevertheless, I'm also glad to see that it looks like Sony are still in the ereader game. Will I be able to resist when the time comes, I wonder?

[plib]

Originally Posted by jackie_w

For anyone who isn't satisfied with the reading experience on the PRST1, you could consider installing Morkl's modified reader app. It installs easily on both non-rooted and rooted devices which are using the latest Sony firmware v1.0.04.12210:

• custom fonts now work properly, i.e bold & italics no longer disappear when setting font to anything other than 'Original'
• can customise all 7 fonts (Original plus the 6 select-a-font) to your personal favourites
• fine control over font-sizes - choose your own 8 sizes
• control number of pages between each full page refresh
• option to make clock visible from within each book

Nevertheless, I'm also glad to see that it looks like Sony are still in the ereader game. Will I be able to resist when the time comes, I wonder?

That actually sounds like just a subset of what is available on the Kobo. I'm surprised that Sony, who have been in the game for longer, have such limited standard firmware. Plus I feel quite chuffed that I went with the Kobo.

[JSWolf]

But with a Kobo, you can't do such changes as you need to be able to specify the new font in the body style. The Kobo doesn't allow this in the CSS. It's a MAJOR bug that Kobo refuses to fix.

[plib]

Originally Posted by JSWolf

But with a Kobo, you can't do such changes as you need to be able to specify the new font in the body style. The Kobo doesn't allow this in the CSS. It's a MAJOR bug that Kobo refuses to fix.

OK, that one zinged over my head a little. I'm not that well up on CSS. All I know is that I can change the font face for the text, change the font size, margins, line spacing and justification, plus the page refresh frequency and the configuration of the screen for the touch to advance, go back and menu areas. So far that has served pretty well for what I've wanted to do.

What's the advantage of being able to specify the font in the body style and, if I was capable of editing the CSS in the epub, why wouldn't Kobo recognize a changed CSS? Genuine questions, at some point I'm going to have to learn to play with CSS and other epub tools.

[Ravensknight]

well, I suspect I just got stuck with a white T1 then. Blast, shouldn't have bought it...

[JSWolf]

Originally Posted by plib

OK, that one zinged over my head a little. I'm not that well up on CSS. All I know is that I can change the font face for the text, change the font size, margins, line spacing and justification, plus the page refresh frequency and the configuration of the screen for the touch to advance, go back and menu areas. So far that has served pretty well for what I've wanted to do.

What's the advantage of being able to specify the font in the body style and, if I was capable of editing the CSS in the epub, why wouldn't Kobo recognize a changed CSS? Genuine questions, at some point I'm going to have to learn to play with CSS and other epub tools.

Most eBooks that use embedded fonts put the font-family for the main embedded font in body. So because Kobo doesn't recognize this, the eBook may not properly display.

[plib]

Originally Posted by JSWolf

Most eBooks that use embedded fonts put the font-family for the main embedded font in body. So because Kobo doesn't recognize this, the eBook may not properly display.

But it would still use the chosen font for display rather than the embedded font? So the display might not be exactly as the author/publisher intended but it's still displayed correctly within the limits of the font chosen on the reader? I'm going from memory but I'm fairly sure I've had font variations, italics, bold, etc. displayed correctly in some books I've read.

If this is kindergarten stuff just ignore me till I've learned CSS.

[JSWolf]

Originally Posted by plib

But it would still use the chosen font for display rather than the embedded font? So the display might not be exactly as the author/publisher intended but it's still displayed correctly within the limits of the font chosen on the reader? I'm going from memory but I'm fairly sure I've had font variations, italics, bold, etc. displayed correctly in some books I've read.

If this is kindergarten stuff just ignore me till I've learned CSS.

But sometimes a font is embedded so the eBook can display certain characters and it's not for sure that your default font will have these.

Also, in some cases, like 11/22/63, the main embedded font is important to give the eBook a certain look and to be honest, it would not look as good with a different font.