Quote:
Originally Posted by kacir
At point 1.
I do agree that that legalese is ugly.
I do not think, however that we should remove it entirely.
I suggest moving it to the end of the file and placing a line like this "for licence see bottom of file" instead.
|
If we move to the end, we can put in a ToC entry to it in case anyone does want to read it.
Quote:
At point 4.
I personally do not like fancy headers. When I format book for myself I remove all fancy formating from headers.
|
My way of doing it.. main text in serif font and headers in san-serif and larger with bold (I think). Nothing fancy is needed. Just an easy way to let us know this is a chapter title.
Quote:
at point 8.
This is again a matter of personal preference. Fully justified text does *look* better. When it comes to hours and hours of continuous reading many people find those "ragged" left justified paragraphs easier to read.
|
Personally I prefer justified with small margins or no margins (on the Sony Readers)
Quote:
point 23.
Here again I have to politely disagree with you
|
I do have headers and /or footers for the books I create in LRF. But there i no need for these in the actual text. It just makes it like a converted PDF where we then have to strip it out. In my case Book Designer or html2lrf creates the headers/footers without them being in the text.
Quote:
point 24.
set page margins as small as possible. We have paid a lot of money to have the screen as big as possible. So why do we want to waste 20% of the screen real estate by margins. Wide margins make sense in a printed books. Reader, however, has "built in margin" around the screen. This is the issue that bothers me the most when I see e-book from the connect store
|
I have been taking to setting the margins to 0 as I like to have as much on screen as I can fit. And it takes less pages and less battery to read a given book that way. Wide margins annoy me. On a paper book, there are reasons for the margins and they are fine. But on a reading device, it makes n sence to have wide margins.
Quote:
point 25.
Use sans serif font. Just like with fully justified text the serif font looks better in a printed books. In a low resolution display (and anything below 300dpi *is* low) the sans-serif font is much more readable.
|
This is personal preference. I like the serif better.
Quote:
|
If you want to use Microsoft Word for formating the documents, beware. Microsoft products use symbols (like left and right quotes) that are not according to standards. This is most notable when you use standards compliant browser (like Firefox) to view html page that was generated using MS Word. Or, if you have text with fancy curly quotes and you upload it an an rtf file to the reader. Plain, simple, basic quote " does not look as nice as typographical one, but it will display correctly on any reading device.
|
The MS Word generated curly quotes do work in Book Designer for generating LRF and Mobi format books.