We are currently experiencing payment processing issues. Our team is working to resolve the problem as quickly as possible. Thank you for your patience
Thread title screwed up?
0
So I was browsing this thread I made about the anime Honey &Clover, and then I saw the title like this:

And I was like "Why is the title all screwed up?"
But then when I went to make a reply:

The title is right here (and only here. Even when I look at the title of the thread in the anime section it's still screwed up).
So, what exactly is happening here?
edit: As Tsurayu mentioned, it seems to be a problem with the & character.

And I was like "Why is the title all screwed up?"
But then when I went to make a reply:

The title is right here (and only here. Even when I look at the title of the thread in the anime section it's still screwed up).
So, what exactly is happening here?
edit: As Tsurayu mentioned, it seems to be a problem with the & character.
0
This bug has already been addressed in private, the problem is that it's parsing & as & for url safe encoding, but it isn't doing that properly on the topic page..while it is elsewhere..
Since it isn't a big bug it's priority is probably pretty low on the fix list.
Edit: Actually just did a test, it seems it is not an issue anymore, my guess is that when Jacob was fixing another HTML-related error in posts that had to do with parsing, this happened, it probably just named your topic that when you posted it because of this issue..
So from this point onward it shouldn't be an issue, and simply renaming the topic to Honey & Clover should correct it.
Since it isn't a big bug it's priority is probably pretty low on the fix list.
Edit: Actually just did a test, it seems it is not an issue anymore, my guess is that when Jacob was fixing another HTML-related error in posts that had to do with parsing, this happened, it probably just named your topic that when you posted it because of this issue..
So from this point onward it shouldn't be an issue, and simply renaming the topic to Honey & Clover should correct it.