Showing posts with label Eric Bower. Show all posts
Showing posts with label Eric Bower. Show all posts

Tuesday, February 27, 2018

The Wonderful Baron Doppelgänger Device by Eric Bower


Rating: WARTY!

This is from an advance review copy for which I thank the publisher.

I have to say up front that I was disappointed in this novel aimed at middle-graders. Maybe a portion of middle-graders will like it, and obviously I am not its audience, but I've read a lot of middle grade novels and found very many of them amusing and/or engaging in other ways. This one didn't resonate with me from the start. It's apparently number three of a series (The Bizarre Baron Inventions) and I'm not a series fan at all, but from what I can tell, it can be read as a standalone, which is how I came into it.

The first problem I encountered was with the formatting, although this isn't what garnered it a less than enthusiastic review in my case. This book, like many such books I've reviewed, fell prey to Amazon's crappy Kindle app, which simply isn't up to the job of fairly representing books unless those books have pretty much been stripped of everything that renders them as anything more than totally bland. Kindle format cannot even handle routine formatting, let alone specialty items like drop caps. Spacing between sections is random at best, and the formatting of this book in the Kindle was atrocious on my iPhone.

In the contents (why is there even a contents page - it's a novel for goodness sake?!), chapter two was run right into the end of chapter one, rather than appear on a new line. Chapter three was randomly indented on the next line. Chapter four was not a link, so you couldn't tap it to actually go to chapter four, whereas other chapters were links, but only a part of the chapter title was actually a URL. So - the usual Kindle disaster.

There wasn't a return tap either - to get back to the contents from the chapter title. Given that ebooks have bookmarks and a search function, I see no point in a contents page! It’s a brain-dead feature of the ebook system which makes zero sense and was obviously designed by a committee. It’s even more pointless if it doesn't work and Amazon seems determined to undermine it with its Kindle system anyway.

The book looked much better in Bluefire Reader in a different format, but even there, there were problems. It was all but unreadable on a smart phone because the pages were represented as a whole entity, which was far too small to read comfortably (at least for me who does not possess the eyes of a falcon!). You could stretch the pages to make them larger and more readable, but then you couldn't swipe to the next page without shrinking the page back to its original size first, so this made for an irritatingly ritualistic reading experience risking carpal tunnel syndrome just from continually stretching, shrinking, and swiping!

I am sure that on a tablet this would work much better, but for me, a phone is usually more convenient and I always have it with me, so I read the Kindle version and tried to ignore chapter titles that had random caps in them, such as chapter 2 which was titled " wHy would a Horse wanT sequIns on ITs HaT?" You see it appears to be only certain characters which are capitalized - the H and the T in this case, so maybe it's not so random. Why this occurs though, I do not know. I have seen it annoyingly often in Kindle.

The Bluefire view presumably represented how the print book would look, but for me this had problems too. In the electronic version, abusing trees by having too much white space isn't an issue, although a longer book does require somewhat more energy to transmit, so there's an issue of energy abuse.

As far as the print version goes, as judged from the Bluefire Reader, the margins, top, bottom, left, and right are super wide, and the chapter title pages have such huge chapter titles that the actual text doesn't start until the last third of the page. There are also illustrations which do little to augment the text and could have been omitted. More on these later. I calculated that there is about a third of each page (and more on the chapter title pages) which is white space.

The fact is that we cannot afford to abuse trees like this in an era of rampant climate change. Each printed book releases almost nine pounds of carbon dioxide into the atmosphere and printing books topples over thirty million trees every year. An e-reader is also harsh on the environment, but once you read a couple of dozen books on it, you’re getting ahead of the print curve. An electronic book takes three times fewer raw materials and uses seven times less water, but even so, the design of your book can make a huge difference.

No one wants to read a print book where the text is so jammed together that it's hard to read, but in this case, instead of blindly following rote rules of one inch margins on all sides (or whatever), making the margins smaller would have shortened the novel significantly, and for a large print run, saved more than a few trees and many pounds of CO2. It's worth thinking about if you care about the planet.

The novel is 237 pages (judged by page numbering in the Bluefire Reader), but it actually starts on page nine and finishes on page 234, so it's really about 225 pages. Tightening the margins and reducing the number of empty pages at the beginning of the novel could have brought this book down to well under two hundred pages (and even with the book-end fluff pages).

Authors and publishers need to seriously consider what they're doing to the environment. To my knowledge there are no fixed rules about how a book should look except what individual publishers 'prefer' so this should be a no-brainer: environment first, formatting second. Save trees, save energy on print runs, and guess what? Save money in producing the novel!

Another formatting issue was that the page headers (the author's name at left, the book title at right) which looked fine in the Bluefire version, were interposed with the text in the Kindle version. For example, one page had this text over three lines:
...said P. "I
erIC bower 29
heard you tell my wife that...
As you can see, the Eric Bower and page number are in the middle of a sentence, and the 'IC' in Eric is randomly capitalized. Why is it even necessary to put the author's name and book title as headers? Do authors and publishers think the reader has such a short-term memory that they need to be reminded every page what they're reading and who wrote it? Again, it's antiquated, hide-bound tradition and nothing more. It serves no purpose.

Back to the image issue I mentioned: completely and predictably mangled the images. They looked even worse on my phone because I keep the screen black, and the text white to save on the battery (it takes more power to keep the screen white and the text black), so the images (on a white background) always look out of place, but it gets worse! On page 21 of the Bluefire version, there is a line drawing of an airplane. This was chopped into segments which were then distributed over seven - count 'em seven! - screens in the Kindle app on my phone! Consequently, the image was largely unintelligible.

The same thing happened to an image of a car. Curiously, the 'monkey in the plumed hat' image, which appeared shortly after the airplane image, was not completely Julienned, but it was split over three screens, and there were black lines across it so it looked like Kindle was thinking about making a jigsaw out of it, but never quite got around to it!

Finally the story itself: it honestly felt just too silly and improbable for me. It seemed less like a story than it was a series of skits jumbled together, and it was larded with so much asininity and so many meandering asides that it was hard to follow the story (and in this I am graciously assuming there was one). It was too silly to read. I reached about forty percent and had to give up on it because it was simply not entertaining and the story appeared to be going nowhere.

Maybe the target audience will go for this, but my kids, who are now a bit older than this target audience admittedly, would not have found this engaging. Personally, I didn't like the main character at all. I felt that first person voice was the wrong voice for this story. It usually is the wrong voice, and is way over-used, but in this case it was made worse because he was just so annoyingly voluble and so repulsively full of himself, proud of his incompetence and trouble-making, and never once sorry for what he did to people.

In fact it was when he was all-but strutting with pride over dropping a fountain pen onto someone's head so that it became permanently stuck there, that I gave up on the novel. He never once exhibited remorse or guilt, and I'm sorry, but this is not the kind of thing you need to be teaching impressionable young boys. At this point it was just too dumb for me to continue and I gave up on it. I cannot recommend this novel based on what I read of it.