It is nevertheless causing users to assume that IABot removed the non-breaking whitespace and it obscures the fact that there is a non-breaking whitespace in the sourcecode. Would it be feasible for IABot to encode whitespaces and other "invisible" characters within template parameters?
That would mean I would need to map every invisible character. This creates code bloat and I would need to find out what every whitespace out there even looks like in it's encoded form. I really think this would be better served by creating an FAQ entry about this instead. I have been grinded on in the past for leaving behind HTML entities rather than decoding them.