PM errors

[Remster 24]

Hey there, Dropzone admins ,

I just got a PM from a certain Brit, and here's the copy paste of the stuff thats really weird in her PM:

Quote

Hi – how’s things?

Wonder if you can help…

That "&#" stuff looks like some sort of character problems.... maybe from the new russian set? But these words would not have been in special characters.... wierd...

Remster

[Remster 24]

Looks like it appears in posts:

http://www.dropzone.com/cgi-bin/forum/gforum.cgi?post=1303350#1303350
The original post shows an appostrophy in:

Quote

I don’t

and the reply in the quote shows a funky &# code in

Quote

I don’t

Remster

[bob.dino 0]

Looks like unicode character strings. What browser & OS are you using?

More (technical) details

[Remster 24]

Quote

Looks like unicode character strings. What browser & OS are you using?

More (technical) details

XP and MS Explorer 6. With SP2.

I agree, it does look like unicode strings, and I figure its an effect of the new russian character set. I'm still using the standard set as I need to use the french accents.

Remster

[sangiro 4]

Quote

and I figure its an effect of the new russian character set

Actually, the way this is set up, your browser will only use the "Russian" encoding if you select Russian as your language in your profile, if not your browser will use standard encoding, so you will never see any impacts of the Russian character set.

This is something else. I need to look into this...

We had some issues with the indexing through the search server for a few days.. could be related. Not sure.

Safe swoops
Sangiro

[Remster 24]

But is the link I posted to a forum thread shows the same strings to everyone, or am I the only one with this problem? (I know I have several non-related problems lmao)

Remster

[sangiro 4]

Nope - I can see the same problem.

Safe swoops
Sangiro

[bob.dino 0]

In this particular case, I'd say the appearance of the unicode artifact is related to something the reply poster did, rather than your browser.

It's be interesting to quiz them on their browser+os combo. And if they cut 'n' paste out of their browser or not.

[bob.dino 0]

A solution would be to use UTF-8 everywhere. Two problems I can think of though:

1- You may have to reencode everything in the database, if it's encoded in incompatible codepages.
2- UTF-8 support seems to vary across browsers and platforms. And I've not, as yet, found a comprehensive list of what's supported where. (This is why I don't do web development for a living ;-)