The Grand Experiment!

[zelda_pinwheel]

Originally Posted by omk3

Because the indent should be relevant to the font size I suppose, but the margin shouldn't...

to put it succinctly, yes, exactly (but i think you mean "relative to" not "relevant to").

[omk3]

See, I'm learning!

[zelda_pinwheel]

Originally Posted by omk3

See, I'm learning!

...

[JSWolf]

So then, I'll just stick with 1.1em for my indent. and change the @page to ...

@page { margin-bottom: 0;margin-left: 15px;margin-right: 15px;margin-top: 15px}

[zelda_pinwheel]

Originally Posted by JSWolf

So then, I'll just stick with 1.1em for my indent. and change the @page to ...

good plan.

[JSWolf]

Originally Posted by zelda_pinwheel

good plan.

Please reread my post. I've edited it since you've quoted it.

[zelda_pinwheel]

Originally Posted by JSWolf

Please reread my post. I've edited it since you've quoted it.

heh. i thought you were making a joke about my example. anyway, i still think that is a good plan (only now i'm being serious). and 15px is a better margin than 0, definitely.

[JSWolf]

Originally Posted by zelda_pinwheel

heh. i thought you were making a joke about my example. anyway, i still think that is a good plan (only now i'm being serious). and 15px is a better margin than 0, definitely.

I'm suggesting that @page in the CSS for those who do want some sort of margin. And to be honest, I don't see a need for a bottom margin given that most readers have a status line of some kind and thus, the last line of the screen won't be at the actually bottom (for example, Sony Readers)

[zelda_pinwheel]

Originally Posted by JSWolf

I'm suggesting that @page in the CSS for those who do want some sort of margin. And to be honest, I don't see a need for a bottom margin given that most readers have a status line of some kind and thus, the last line of the screen won't be at the actually bottom (for example, Sony Readers)

sure, although depending on the display, it might be necessary to add a bit of bottom margin to separate the text from the status line. as for the rest, 15px margin is a minimum for me, and lately i've been preferring even a bit more. i know a lot of people prefer less.

[JSWolf]

Originally Posted by zelda_pinwheel

sure, although depending on the display, it might be necessary to add a bit of bottom margin to separate the text from the status line. as for the rest, 15px margin is a minimum for me, and lately i've been preferring even a bit more. i know a lot of people prefer less.

On the 900, I can see a lot of people using no margin as there is no right side page number. I don't mind the occasional overlap as I'm fine at reading what overlaps.

[ShellShock]

Originally Posted by daffy4u

[*]Page Turn buttons: better on K2, little tiny side button on 505 side in wrong order (for me) and are too small, big round button on bottom right does not turn pages in books (it should), big round button on the left is awkward for me.

I totally agree, but it can be changed. When you use PRS-Customizer to get an image of your firmware, you should have a applicationStart.xml file in the opt\sony\ebook\application\resources directory. Edit this file and change:

<boolean key="0x27" do="doCenter"/>

to

<boolean key="0x27" do="doNext"/>

If you flash this firmware now, the big round button on the right will do a page turn (forward). Holding the button will give its former function, e.g., after entering a page number using the number buttons, hold the round button and you will go to that page.

[kennyc]

I just for the first time had to use my K2 in place of my Sony. The 505 does not search, and I needed to find a particular passage. Converted the book to mobi and used the K2....

I think this one experience is almost enough to tip me over to the Sony 900 purchase.

[daffy4u]

Originally Posted by ShellShock

I totally agree, but it can be changed. When you use PRS-Customizer to get an image of your firmware, you should have a applicationStart.xml file in the opt\sony\ebook\application\resources directory. Edit this file and change:

<boolean key="0x27" do="doCenter"/>

to

<boolean key="0x27" do="doNext"/>

If you flash this firmware now, the big round button on the right will do a page turn (forward). Holding the button will give its former function, e.g., after entering a page number using the number buttons, hold the round button and you will go to that page.

Thanks for the heads up shell shock. I actually made the button do what I needed with PRSPlus. My pro/con list was based on the K2 and 505 *before* any hacks were applied.

[JSWolf]

So Daffy, are you hooked on ePub yet?

[daffy4u]

Originally Posted by JSWolf

So Daffy, are you hooked on ePub yet?

I have to say "no". For the books I read and my reading style (YMMV), ePub is just another eBook format. I still have not found the necessity to purchase a book in ePub. Even if I didn't know how to format shift, it is still very easy for me to live on mobi books alone.

Right now, Sigil give ePub the advantage of being able to correct mistakes in ePub but I'm not as picky about formatting as some. As long as no freaky characters pop up (gibberish), spelling is mostly good and there aren't huge line spaces between paragraphs, I pretty much good to go.

From what I'm gathering about the MobiUnpack script pulling html from mobi books (if I understand correctly), it will be easier to correct mobi books as well.

It's a wash.