Check .....?

[1eduard]

Is the best way to write my e-book on the computer and check it on smartfones/tablets (e.g. I've a Samsung smartfone/Android)?

[JSWolf]

Originally Posted by 1eduard

Is the best way to write my e-book on the computer and check it on smartfones/tablets (e.g. I've a Samsung smartfone/Android)?

You should also check your eBooks on Kobo, nook, and Kindle Readers. Good luck finding a program that respects the CSS.

[1eduard]

But that's impossible here in The Netherlands!

Is it possible that someone checks for me in the U.S.?

[JSWolf]

Originally Posted by 1eduard

But that's impossible here in The Netherlands!

Is it possible that someone checks for me in the U.S.?

You could do without the nook given that you are not in the US. But you can buy a Kobo and Kindle from Kobo and Amazon in the Netherlands. So it's not fully impossible.

[1eduard]

Yes, it is! Now I don't have money to buy devices.

[theducks]

Originally Posted by 1eduard

Yes, it is! Now I don't have money to buy devices.

That is why many pay Pros, who do have devices. (they also have developed a toolkit if tricks to make things work. Or ADVISE you that is a bad idea!).

If you start with a clean (simple formatted) EPUB, you might save money, while getting a decent product.

By simple, I mean, no really fancy styling like hardback books sometimes do.
Bold, Italic, Flush, Indented, blockquotes and Chapter headings
As a matter, NO style=, no CSS just means you take the devices default, and that might work.

Drop caps, Tables, images, lists (li) all take a bit of fuss

[JSWolf]

Originally Posted by theducks

That is why many pay Pros, who do have devices. (they also have developed a toolkit if tricks to make things work. Or ADVISE you that is a bad idea!).

If you start with a clean (simple formatted) EPUB, you might save money, while getting a decent product.

By simple, I mean, no really fancy styling like hardback books sometimes do.
Bold, Italic, Flush, Indented, blockquotes and Chapter headings
As a matter, NO style=, no CSS just means you take the devices default, and that might work.

Drop caps, Tables, images, lists (li) all take a bit of fuss

I agree to keep the code as simple as possible. Even if you use styles when using the word processor, you still may need to edit the HTML/CSS code after the eBook is converted to ePub.

This is the CSS code I always add to the CSS because it's what I use where needed.

Blockquote is for offset text.
.blockquote is for offset text that is at the end of the chapter. <blockquote class=blockquote>
body is the main style for the entire eBook.
img makes sure the images do not expand larger then the screen/window.
p is the settings for most paragraphs without the need for a class.
hr is for section breaks <hr/>
.cover is for making the cover image and other images full screen <div class="cover"><img alt="" class="cover" ../images/cover.jpg/></div>

blockquote {
  margin-top: 1em;
  margin-right: 1.5em;
  margin-bottom: 1em;
  margin-left: 1.5em;
}
.blockquote {
  margin-top: 1em;
  margin-right: 1.5em;
  margin-bottom: 0;
  margin-left: 1.5em;
}
body {
  widows: 1;
  orphans: 1;
  margin-top: 0;
  margin-right: 0;
  margin-bottom: 0;
  margin-left: 0;
  text-align: justify;
}
img {
  max-height: 100%;
  max-width: 100%;
}
p {
  margin-top: 0;
  margin-bottom: 0;
  text-indent: 1.2em;
}
hr {
  margin-top: 1em;
  margin-right: 40%;
  margin-bottom: 0.9em;
  margin-left: 40%;
  border-top: 2px solid;
}
.cover {
  text-align: center;
  text-indent: 0;
  height: 100%;
}

[1eduard]

Ok, many thanks!