Adobe Dreamweaver is rewriting code... again.

Question

http://www.cfinternals.org/blog/2012/02/dreamweaver-cs55-rewrites-code-again.html
I just upgraded from Dreamweaver CS5 to CS5.5, as I needed to cross-grade to the Design Suite in order to get InDesign.
Everything was going swimmingly, until I ran across the following. Take a look at the following code fragment:
<input type="text" name="getEmailAddress()" size="40" required="1"validate="email" message="Please enter your email address." />
Thing is, this is NOT HTML. This is part of an XML definition of a form, embedded within a CFC. Whenever CS5.5 gets its grubby little paws on it, however it changes it to this:
<input type="text" name="getEmailAddress()" size="40" required validate="email" message="Please enter your email address." />
Note the required="1" attribute is now simply required. Which blows up the XML parser big time.
This, just when I was getting around to writing a post about how, after THREE versions (CS3, CS4, CS5), Adobe finally got around to fixing the code rewriting bug I originally posted back in March, 2008.
I've tried changing doctypes, turned off rewriting in preferences, and done pretty much eveything I could think of, AND DREAMWEAVER STILL REWRITES MY CODE!
Look, Adobe, I'm a professional. I know what I'm doing, and when I put text to a file, I expect it to remain exactly as written. I do NOT need you "improving" my code.
Especially when "improving" my code BREAKS MY CODE.
Please provide a "hands off" option, and HONOR it.
I wonder how many years I'm going to have to wait to get THIS fixed...

Answer 1

I don't care if it's known or not. I want it FIXED. I want Dreamweaver to stop rewriting my code. The fact is that these kinds of behaviors have been "known" since CS3... and they have gone on for years... and they are ALL unacceptable.
And why is Dreamweaver performing these kinds of changes based on the presence of a doctype specification... in a CFC??????
One other thing. I saw your comments on this in another thread, and the one that got me was the one that said, "And this is a problem how?"
Like I said above, we are professionals. Dreamweaver is supposed to be a tool for professionals. We know what we're doing, and when we write code, we expect it to remain exactly as written, unless we specifically ask for it to be reformatted. We do NOT need Dreamweaver silently cleaning up or "improving" our code. Doing so is not a feaure. It is not a benefit.
Especially when it breaks it in the process.
You can pass THAT along too.