Users with spaces in the username not accepted as valid recipients

I think the patch is good, but IMHO for the wrong reason. It does not strip spaces, unless someone translated '[user]' with at space.

+++ b/privatemsg.moduleundefined
@@ -981,7 +981,7 @@ function _privatemsg_parse_userstring($input, $types_limitations = array()) {
 function privatemsg_privatemsg_name_lookup($string) {
   // Remove optional user specifier.
-  $string = trim(str_replace(t('[user]'), '', $string));
+  $string = trim(str_replace('[user]', '', $string));

What is t('[user]') doing here anyway? The string should not be translated at all, it is a token. It is not even the value of the token.

Patch should not be accepted "as is" because of the issue with t() noted in #3.

@ptmkenny, but what problem are we solving here? In my view the patch is good, because it removes an unwanted t().

Ah, sorry, I misread your comment. Setting it back...

Committed and pushed to all relevent patches, thanks for testing.