Comment 2 for bug 317409

I'm assuming the stuff Christophe was working on is actually now in the tree.

This bug is still open, though, since in the current scheme on things one case set the replacement character once, but cannot handle individual ones or capture decoding errors in the first place.

Adding this doesn't look hard in the current scheme of things, though.