In several locations, you might have problems when a user writes over the hard character limit (i.e. 50 in the title) with an multibyte character.
In this case, the char will "break in two" with only the first part saved... an invalid char.
As I just had with a clan motd, this can mean you can display it with the wrong char at the end (an ? normally as the browser can't interpret that) but an textarea box i.e. will be empty... because the htmlentities function will return nothing there...
Solution: remove the last character and it will work again.
I don't know if I do a complete core solution to work with those char problems... it's hard to grab as html elements only take "char" as counter, and char=1 for them, they don't calculate *how much space* I need in the database.
However, we could simply scale the DB fields larger, to fetch and save such overheads. In the clans,however a substr() is done which breaks it

an mb_substr would suffice.