As it stands, you just said that 6 out of 11 problems are down to people, and epubmaker can't fix them.
I don't remember suggesting that epubmaker should be the place to fix these problems. Rather, what I suggested was that the problem *should* be fixed, that the problem has been going on for years, that the problem isn't getting fixed, and PG doesn't have an approach to fixing the problem. I would hope by now we can all agree that epubmaker is being sent on a fool's errand. What I have been suggesting is simple: When someone submits HTML which is broken on one or the other major platforms, then a PG volunteer who is interested in fixing the problem should be allowed to do so, while maintaining as much of the existing formatting as possible. IE formatting errors, just like scanno errors, should be something that is fixable. In practice fixing formatting errors is probably going to require submitting a new entire file because both the CSS and the markup will be involved. WW'ers can review the changes for sanity by doing a diff, like always. Let me restate the opposite position: Why should someone who insists on submitting broken HTML have the right to monopolize a good *public domain* book forever, such that PG can never distribute that book in a way that can pleasantly be read on all the major platforms ??? Another way of saying it is this: PG should set an expectation that submitted HTML should run in an attractive and pleasant manner on all the major platforms, or PG reserves the right to fix the problem. That isn't a "snowflake" problem, rather it is an *anti* snowflake statement: What you write once should be readable everywhere, and it should not show up in a "scambled eggs" "snowflake" variety messed up in a different manner on each and every one of the different platforms. If "vanity" keeps PG from being able to fix broken HTML, then we have real problems. In summary: Give us a real way to fix broken formatting.