I've done some tests in this area. And yes, I'll agree, the bloat that is generated between traditional print based layouts and the web can be very daunting (RIP mso). But, I've also found that if you utilize the proper layout and styling commands to start with, the transition can be a lot less painful. ;)
Still, we all know Microsoft is notorious for generating code bloat between it's desktop applications and web. I would imagine that happens with most conversions, no matter what. There is a cleansing process that needs to be performed and if the original author is aware of those challenges, they can adequately prepare for and minimize the impact.
I've tested multiple document to web conversion utilities. None of them are perfect. I wouldn't use any of them either. Microsoft doesn't make it easy for us clean code fanatics. I've learned over the years to just
Ctrl+A, Ctrl+C, Open Notepad++, Ctrl+V, Ctrl+A, Open FrontPage, Ctrl+Vand begin the reformatting in Design View (WYSIWYG), then switch to Code View, format my HTML via a right click function and off we go! It's a lot simpler than jumping through all the hoops to deal with HTML code bloat.
Most of today's Editors give you the ability to customize your workspace. With FrontPage/EWD, you have control over everything. If you don't customize your editing environment, you're going to face challenges moving forward. Few Editors are perfect out of the box. There's a lot of guessing that goes on when you start pushing buttons. With FP, if you push those buttons in the wrong sequence or do something you were not supposed to do, well, you (not you directly) deserve what happens. The software is only as good as the user. :)