ePUB weight

[eschwartz]

Originally Posted by JSWolf

I put the justify in the body style. As for the font-family, I would not have put it in unless it goes with an embedded font. The font-size, I would dump as well. Also, the 0.00em should be just 0. The text-indent also is too small. I use 1.2em.

body {
oeb-column-number: 1;
widows: 1;
orphans: 1;
margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
text-align: justify
}
p {
margin-top: 0;
margin-bottom: 0;
text-indent: 1.2em
}

This is code I use.

justfication, like fonts, is something that should be determined by the device settings unless there is a peculiarly compelling reason in that specific case to specify it.

Just my $0.02

Some people prefer justified, some people prefer ragged right, and who are you to override their device settings just because you prefer it?

Set it in your own device settings and leave the default unspecified.

[JSWolf]

Originally Posted by eschwartz

justfication, like fonts, is something that should be determined by the device settings unless there is a peculiarly compelling reason in that specific case to specify it.

Just my $0.02

Some people prefer justified, some people prefer ragged right, and who are you to override their device settings just because you prefer it?

Set it in your own device settings and leave the default unspecified.

Not all devices give you a choice. Not all programs give you a choice. Not all programs default to justify. Some default to left justify. I don't know what Kindle's default to, but they do not allow changing the justification. Sony Readers do not have that option (I forget what the default is). So many people might end up with left justify and I do think more people would prefer full ten left.

[Toxaris]

Most of the time I put in 'font-family: serif;'. When reading, I like serif much better than sans-serif for normal reading. And, the reader can still choose a font if they want another.

[Notjohn]

The Kindle default is justified. As a result, we sometimes see a Look Inside sample on the Amazon store that is ragged right while the downloaded version turns out to be justified. This is presumably a result of not specifying text-align=justified in the style sheet. (Look Inside follows its own rules in several respects.)

[saguay]

I dont know and he is on the road for his work.

[saguay]

Thank you

[saguay]

If you included this in the body:

body {
oeb-column-number: 1;
widows: 1;
orphans: 1;
margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
text-align: justify
}

What happenned to the h1,2,3... They justified ?

[saguay]

And what is the meanning of :

widows: 1;
orphans: 1;

[DaleDe]

Originally Posted by saguay

If you included this in the body:

body {
oeb-column-number: 1;
widows: 1;
orphans: 1;
margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
text-align: justify
}

What happenned to the h1,2,3... They justified ?

They would be if they are longer than a single line unless there was a CSS entry specific to h1,2,3. Headings are often shorter than a line and they would be left justified just like the last line of a paragraph.

widows and orphans entry sets the number of lines that must be on a page together when a paragraph is split near the end of a page. The ADE default is typically 2 so setting this to 1 will allow a single line in a paragraph to appear at the bottom of the page and also at the top of the next page (basically it turns off widow and orphan control).

Dale

[saguay]

Thank you. And what will happend to :

<p class="break">* * *</p>

[DoctorOhh]

Just my unprofessional opinion, but I still think that paragraph justification should be left out of the CSS and let the device or reading program handle justification.

[DaleDe]

Originally Posted by saguay

Thank you. And what will happend to :

<p class="break">* * *</p>

It depends on what the CSS for break does. I would assume you will have a center in that CSS to override the default set up in body.

Dale

[DaleDe]

Originally Posted by DoctorOhh

Just my unprofessional opinion, but I still think that paragraph justification should be left out of the CSS and let the device or reading program handle justification.

I prefer that myself. Normally there is a setting in the app that will do what the reader wants. For my phone I typically use left justified due to the narrowness of the screen and the increased use of hyphens when fully justified or the huge spaces between words.

The argument for making it like the book doesn't cut it when the eBook justifies based on whole spaces between words while the book was able to adjust tiny spacing between letters and small increments of space size as needed. I have yet to see an eBook reader with that kind of refinement.

Dale

[Notjohn]

The problem with not specifying justification is that on the Amazon store, such a book will have a ragged right Look Inside preview, while the downloaded book will be justified.

I went through last week's e-book best-seller lists in the Wall Street Journal and found three instances (out of twenty) where this was the case. (All twenty books were justified. To me, that's sufficient reason to specify justified alignment.)

In the past year or two I have read two ragged-right books from major publishers, one being a Daniel Silva thriller and the other being David Mamet's rant about The Secret Knowledge. Neither irritated me sufficiently to return the book (I only paid for the Mamet; the other came from the library) but I was conscious all the time that I was reading what, to me, seemed an amateurish production. Perhaps that's because I've been reading justified books for more than seventy years, and I expect e-books to be as professionally done.

By contrast, the occasional short line (more typical in Kindle editions than widely spaced words) doesn't bother me at all.

(And yes, I often read books on my iPhone 4 held horizontally.)