View Single Post
Old 01-04-2016, 09:14 PM   #7
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by ATimson View Post
I've yet to have the "warnings" result in a broken book that I've noticed - I think the typical ones that I see are for either fonts or CSS that Kindlegen doesn't like. But it's able to ignore them and produce a usable book anyways. So for my purposes I'm happy to ignore those (and treat it as a success) - it's only the true errors that I'm worried about right now!
Likewise. The annoying part is that this behavior changed in a Kindlegen update a couple of years ago, and warnings that used to be ignored, resulting in a zero exit code, now result in kindlegen returning 1, thus requiring Makefile changes. I forget when that happened—maybe between 1.x and 2.x.

There's also no real notion of severity for warnings, nor the ability to ignore specific types of warnings that aren't really important, making the separate exit status for warnings much less useful than it otherwise would be.
dgatwood is offline   Reply With Quote