On Thu, Dec 13, 2012 at 10:23 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
Thanks for catching these problems. Two proposed patches
are attached. The first fixes the problems by going back to ASCII.
The second puts in a check for this problem, so that non-ASCII
bytes like that don't slip into future releases. At some point
we may well want to add non-ASCII characters, but they should
be UTF-8 I expect. I've pushed these proposed patches into
the unofficial experimental repository at github.
FWIW, as a Spanish speaker (and possibly the author of the mail messages in Spanish which got converted into Latin-1 encoded comments) I vow for UTF-8 encoding rather than mutilation.