As a friend of mine say 100 of millions can not err, eat shit! flies that is!

If I hazard to attempt to decode the logic of your rhetoric, I think what you are trying to say is that PG ought to only support a subset of those reading devices PG customers, or would-be PG customers, own and would like to read on. Okay, then, perhaps you can list in the below two boxes which machines you propose that PG *ought* to be supporting, and which machines you propose PG *ought not* to be supporting: ========= List of PG supported devices: ============= ========= List of PG *not* supported devices: ======= ===================================================== You can make such a list -- and certainly [privately] I have my own mental list of such devices I think PG ought and ought not to be supporting, BUT, if anyone were to mention such lists publicly then all that happens is "we" engage in endless flame wars. AND, more importantly, "we" would be going around in circles. Some years ago I asked PG to allow me to start posting MOBI formatted files because I thought the personal eBook Reader market was heating up, and was told by the PG "powers that be" to go stuff myself, and if this was something I wanted to waste my time on, I should go make my own website to support such machines. I did go stuff myself and went off and made my own website to support such machines, and so did many other people -- the difference being *the other people* took PG's name off the books, and "down-converted" the formatting of the PG books, throwing away much PG volunteer time and effort, and thawing away some of the original author and publishers intent, while "selling" these books "as their own." Whereas I left PG's name on the books, told people how to donate and volunteer to PG, and didn't "down-convert" the formatting, but rather left as much of the original formatting in place as the MOBI file format supports. And after a couple years of seeing other people getting all the credit for PG's efforts, guess what, surprise, PG decides they had better support MOBI after all. And that they had better support EPUB while they're at it. So, now we "PG" are supporting MOBI and EPUB. Well, what does it take to *actually* support MOBI and EPUB? One better know what the various MOBI and EPUB devices can or cannot do, just like one -- if one thinks one is writing "good style" in HTML -- one better know what the major HTML browser do or do not do with your HTML code on each of the browsers on at least the three better known HTML operating systems, otherwise, guess what -- what the PG customers end up seeing from your "eBook Writing Efforts" is, in practice, garbage.