Gizmo, you may try changing your language encoding to UTF-8 in the language file. Making this change allowed me to PM users with those types of characters. Not sure of another fix yet, but still testing.

Lol now the users username shows up as blocks with qquestionmarks and theres no way to update their display name (as the controlpaneldoesn't use the UTF-8 setting

ok, i 'became this user' and updated their display name, and was able to send them a pm with their special characters...

lol this user in the cp now looks like:

Blah, ok. So the name is probably encoded in the db with another format. I really need to bite the bullet in an upcoming release and just switch everything to UTF8 and then have the upgrader convert the old content as well. Maybe convert all of the time formats to UTC at the same time. Just don't want to have to put out such a major upgrade just yet

Will see if I can find some other fix for this now.

lol, why UTC? I like using the unix epoch

I'm talking about the base timestamp. They will still be stored in unix epoch, but right now they are stored with the adjustment of the server time offset. So, that leads to varying time problems like the one just noted when we switched to daylight savings time

Ahhh, so long as they're stored in unix time I can live with any change... lol...

On all of my scripts I use set-env to set the default timezone to GMT then do the time procesing live; for offsets as well, and daylight savings time, just all the if/else can get kida bulky lol

This seems to be unfixed in 7.1.1, right?

the fix is the UTF-8 characterset, which renders extended characters as odd characters without converting; so it will remain unfixed until Rick can find a way to convert previous posts in the database at once.