Comment 8 for bug 1083418

That translation is correct for that string, and I can't think of any way to say the same with other words without altering the meaning.

In any case, I don't think the problem is in the translation, but in how the programs handle strings. What will happen when somebody translates it to Chinese, Russia, Japanese or Arabic? Those languages make a heavy use of non ascii characters, and many other languages, while still using the Latin alphabet, need non ascii characters (even your surname and my name need them).

Modifying the translation so it doesn't include nonascii characters isn't a fix, but a bad workaround evading the actual bug.