The 470s are adding the spaces into the ends of certain lines themselves, vlans in particular. At command line a space at the end of a line is a registered character. I know someone rebuilt the switch stack in question from the corrupted ascii file by pasting line by line. I did a download of an ascii on a fresh config I built by hand, then used notepad++ to trim leading and trailing white spaces, did a save as version 2. Then used notepad++ to compare and they show up. Someone mentioned exam diff at work, doubted me, exam diff doesn't show white space leading or trailing.
Once again I had to prove myself. Crime scene photos, fingerprints, secret recorded conversations and evil trailing white spaces. If you select a whole line in ascii to load via command line your potentially adding white spaces to lines that already have them. And that switch that was rebuilt from the corrupted ascii, the login prompt is screwed up because of these spaces I mention. Copy and paste from first character to last only.
Case closed
