'best format'?

[xtine]

@Christopher I was actually wondering if I got a lemon, especially since I've read so many raves about the clarity of the 300's screen, but since you're seeing this with your 600 as well, maybe that's just the way it really is.

[ChristopherTD]

Originally Posted by xtine

@Christopher I was actually wondering if I got a lemon, especially since I've read so many raves about the clarity of the 300's screen, but since you're seeing this with your 600 as well, maybe that's just the way it really is.

It is awkward for me, because I have read on VGA smart phones and now iPhone for 4 years and am used to the high contrast backlit LCD, which is more consistent under all conditions. I find the Sony to be vary wildly depending on the amount of and type of light available (naturally enough). Just not used to having to tilt the device to get the right angle!

It is also hard to evaluate because I have yet to really read a book on the Sony, and tinkering with it is a really hard way to make comparisons. I need to immerse myself in a book and see how that works, or if immersion is impossible! I can certainly immerse myself when reading on iPhone to the extent that I can navigate crowded train platforms, ticket barriers and escalators without looking up from my book!

[Solitaire1]

Originally Posted by ChristopherTD

I am puzzled by this as well. The status icons are rich dark black, but actual book text on my PRS600 seems very washed out. If it was blacker I think I would be happy with the device. Clearly the screen is capable of it - perhaps a firmware upgrade will improve matters?

One possible reason is the typeface itself. On my reader, some typefaces display darker than others. That is one of the reasons I render the main text of my ebooks with the Georgia typeface, it shows up as thick and dark on my reader's screen (it's about as dark as the menu text). I also find it a very easy to read typeface.

[xtine]

Thanks, Solitaire, will try changing the font

[Avistew]

Originally Posted by Solitaire1

For me, full justification is fine as long as the size of the text is not too large and the width of the column is not too thin.

I agree with the problem you mentioned, having one word on each end and a huge space in between looks terrible. I prefer when cutting words is activated, in which case long words are cut and it remains justified. If the program cuts them in the right place it's not a problem at all (if it cuts it just anywhere then it can be a problem to read, though).
I don't think lrf supports that, though, do they?
I read a smaller font than you do (usually 9 pts) so I definitely don't have that problem but I can see how a smaller font would make it arise.

[xtine]

Originally Posted by Solitaire1

One possible reason is the typeface itself. On my reader, some typefaces display darker than others. That is one of the reasons I render the main text of my ebooks with the Georgia typeface, it shows up as thick and dark on my reader's screen (it's about as dark as the menu text). I also find it a very easy to read typeface.

I just changed one of my ePub books' font to Georgia and the font is a lot darker now. Thanks again!

[Solitaire1]

Originally Posted by Avistew

I agree with the problem you mentioned, having one word on each end and a huge space in between looks terrible. I prefer when cutting words is activated, in which case long words are cut and it remains justified. If the program cuts them in the right place it's not a problem at all (if it cuts it just anywhere then it can be a problem to read, though).
I don't think lrf supports that, though, do they?
I read a smaller font than you do (usually 9 pts) so I definitely don't have that problem but I can see how a smaller font would make it arise.

I can't speak about lrf since I've never used it to make my own ebooks. When making ebooks, my main experience has been with AporisDoc (the format that the Palm Reader uses, I don't use it anymore since getting my Sony Reader, it would be great is the Sony Reader supported the format), RTF, and PDF. I basically format the ebooks in the OpenDocument format, and then export them to PDF.

I know that hyphenating words (I think that's what you mean by "cutting words") could deal with some of the poor line breaks that occur when flowing the text, both with and without full justification. But I find it more readable to not hyphenate at all. Also, it saves me from having to go through my ebooks and rehyphenate the text it if I decide to reformat them (such as to a smaller font or a different typeface).

One of the best things about ebooks is that its formatting can be adjusted to suit the reader. Since I've begun needing to use reading glasses for smaller print, the ability to increase the size of the text is a definite plus for me.

Originally Posted by xtine

I just changed one of my ePub books' font to Georgia and the font is a lot darker now. Thanks again!

You are welcome. I'm glad to help where I can, and I've found Georgia to be one of the better-looking typefaces. To me, it gives the text a slightly more interesting look than either Thorndale or Times New Roman. Also, I prefer to make the main text of my ebooks in a serif typeface.

[Avistew]

Originally Posted by Solitaire1

I know that hyphenating words (I think that's what you mean by "cutting words") could deal with some of the poor line breaks that occur when flowing the text, both with and without full justification. But I find it more readable to not hyphenate at all. Also, it saves me from having to go through my ebooks and rehyphenate the text it if I decide to reformat them (such as to a smaller font or a different typeface).

I'm used to programs that do it automatically, although I've only seen that in French, I'm realising now. I guess because French has longer words as well as more logical rules for hyphenating, such programs are both more needed and easier to make.
Basically the program decides if it's better to leave a word whole or to cut it, and where to cut it (usually between double consonants, always between syllables).
Since in French one syllable doesn't have any influence on how the previous or next one are pronounced, cutting between syllables doesn't make it harder to read at all.

I'm guessing this isn't supported in lrf though. I know rtf and doc files support it in French though, but all my programs are in English now and I can't find the option to do that anywhere.
I've also been having trouble with special spaces, the type that can't be cut.

For instance in French, double punctuation has one space before and one space after (double punctuation is ";" ":" "?" "!" and French quotation marks). The space before (or after, for opening French quotation marks) cannot be cut (it's a specific one different from a regular space) and needs to be linked to the word before (after) it.
This isn't supported in lrf so you sometimes end up with these symbols at the beginning of a line, which can be very annoying.

It is however supported in doc and rtf as a special symbol, but I'd have to see if these special symbols are recognised on the reader.

If they are, I might end up switching to rtf for my favourite format.

[Solitaire1]

Originally Posted by Avistew

I'm used to programs that do it automatically, although I've only seen that in French, I'm realising now. I guess because French has longer words as well as more logical rules for hyphenating, such programs are both more needed and easier to make.
Basically the program decides if it's better to leave a word whole or to cut it, and where to cut it (usually between double consonants, always between syllables).
Since in French one syllable doesn't have any influence on how the previous or next one are pronounced, cutting between syllables doesn't make it harder to read at all.

I'm guessing this isn't supported in lrf though. I know rtf and doc files support it in French though, but all my programs are in English now and I can't find the option to do that anywhere.
I've also been having trouble with special spaces, the type that can't be cut.

For instance in French, double punctuation has one space before and one space after (double punctuation is ";" ":" "?" "!" and French quotation marks). The space before (or after, for opening French quotation marks) cannot be cut (it's a specific one different from a regular space) and needs to be linked to the word before (after) it.
This isn't supported in lrf so you sometimes end up with these symbols at the beginning of a line, which can be very annoying.

It is however supported in doc and rtf as a special symbol, but I'd have to see if these special symbols are recognised on the reader.

If they are, I might end up switching to rtf for my favourite format.

I used to use RTF for my ebooks, but I ran into a very frustrating problem with typefaces. What I found with RTF files on my ebook reader is that I haven't been able to get it to consistenly display the general default typeface that I want (serif, san-serif, or monospace). With many RTF ebooks, they display in the default san-serif typeface, regardless of the actual font in the RTF file. In the stories that I write, I use specific typefaces to indicate what the text is (main text, character's thoughts, headings, and so on).

That is the main reason that I switched to PDF for my ebooks. I use my word processor to make my ebooks and I can take full advantage for its formatting capabilities (including hard spaces which is one way to solve the double punctuation problem that you mentioned). When I'm finished, I can export them to PDF and they will look exactly they way I want them to. Although I do lose the ability to increase the font size, the control over an ebook is worth the tradeoff.

[HarryT]

Originally Posted by Avistew

I've also been having trouble with special spaces, the type that can't be cut.

For instance in French, double punctuation has one space before and one space after (double punctuation is ";" ":" "?" "!" and French quotation marks). The space before (or after, for opening French quotation marks) cannot be cut (it's a specific one different from a regular space) and needs to be linked to the word before (after) it.
This isn't supported in lrf so you sometimes end up with these symbols at the beginning of a line, which can be very annoying.

LRF format certainly supports the "non-breaking space" (" " in HTML).

[Avistew]

Originally Posted by HarryT

LRF format certainly supports the "non-breaking space" (" " in HTML).

Thanks That's good to know. (I guess I'll have to modify them myself).

[Latinandgreek]

I that lrf seems to have the quickest page turns.