I don't think so Ken, guess it is/was related to some problems with code and how it came through in the e-mail notifications.
I don't know much in this area, and I'm not sure how much depends on the BBCode used here and the Lounge software, and on the other hand standards of Internet (i.e. specification for URLs). Some characters are reserved (in URLs), some are a bit "unsafe" to use, and they must be encoded (or perhaps handled in some other way; didn't we use brackets in the old old Lounge around some characters). In these rare cases I don't think there's much to do, but to encode them.
Anyhow, as Dave said, the curly brackets creates problems, but then we also have a backslash in there.
Replacing:
{ with %7b
} with %7d
and
\ with %5C
in this:
Code: Select all
http://www.google.co.uk/search?q=Unused+File+Extension%09{80b8c23c-16e0-4cd8-bbc3-cecec9a78b79}%09HKCR\{80b8c23c-16e0-4cd8-bbc3-cecec9a78b79}
generates this:
Code: Select all
http://www.google.co.uk/search?q=Unused+File+Extension%09%7b80b8c23c-16e0-4cd8-bbc3-cecec9a78b79%7d%09HKCR%5C%7b80b8c23c-16e0-4cd8-bbc3-cecec9a78b79%7d
And this is the result (your Google search):
http://www.google.co.uk/search?q=Unused ... 9a78b79%7d" onclick="window.open(this.href);return false;
Byelingual When you speak two languages but start losing vocabulary in both of them.