Quote:
Originally Posted by FrustratedReader
A screen shot would have told nothing more except I wasn't making it up.
The only sensible "content creation" tool to write is a wordprocessor. The output has to be PDF for POD and ms .doc or .docx to upload to Amazon. Only Google Books requires ePub upload for Google Play, though they seem to prefer PDF, which is stupid.
|
If you are planning on print documents, sure. If you are not planning on print documents, sensible is not quite the word I would use. As for upload to Amazon, they accept formats other than .doc or .docx. Epub is accepted and gives, in the opinion of several authors I know, the closest match between formating in the input and the azw3 output. The need to unzip the epub before uploading is a bit of a pain. OTOH, have you ever read the Amazon disclaimer on uploading a .doc/.docx file? The one that reads: "
Most DOC/DOCX files convert well to eBooks. However, some files with complex formatting may not convert as well."
Quote:
Originally Posted by FrustratedReader
Paper requires absolute measurements.
|
And a knowledge of what size the output paper is. Is it letter? A4? Tabloid? booklet? No better than using absolute measurements on a webpage where the resolution of the display is unknown.
Quote:
Originally Posted by FrustratedReader
MS doesn't even listen to the feedback on the Insider program.
|
I would disagree there. I've been involved in several Microsoft beta programs. I've found they do listen to the feedback though sheer volume of complaints was the deciding factor. For the Windows 10 and Server 2019 insider programs, the recent ability to flag bug severity is a welcome improvement compared to their older sheer quantity of complaints severity ratings.
Quote:
Originally Posted by FrustratedReader
Sometimes it seems that stuff works differently to last week and you have to change a setting you didn't change ever, or changed it so long ago. I noticed last night after reloading around 1000 books as ePubs instead of kepubs SOME epubs were ignoring the Kobo GUI user setting for Line Spacing. Obviously too tight for accented capitals on a line below descenders. Calibre had 120% minimum line spacing. I tried ALL the options in paragraph style in LibreOffice Writer (no effect). Only setting the minimum line spacing to 0 in Calibre allowed the GUI on the Kobo to increase the line spacing. Obviously while 120% is typical, it's not enough for some combinations of fonts, accented capitals and descenders. Puzzling as I'm sure I used to be able to vary line spacing on the Kobo on ALL the books before. Also "Minimum Line spacing" option sets a line spacing in the body css which the Kobo seems to regard as a fixed line spacing of 120% (or whatever you set it to), ignoring user GUI control.
Overall page L & R margin is adjustable and the same default on the Kobo GUI, no matter what the LibreOffice .odt or MS Word .doc page margins, headers & footers are.
|
That respect for embedded CSS in epubs has been there since the early days of Kobo ereaders. If you specify a line height for an element, the slider will have no effect. The L/R margin slider can only increase the margins specified in the the epub style and not decrease it. If some maroon decides to specify a font size in absolute measurement...
You might want to look into using the calibre editor or Sigil to work on the epub instead of depending on calibre's conversion. Sigil with the preview windows on a second monitor is my preferred environment.