Milovana.com

http://www.milovana.com/webteases/showt ... =920&p=2#t

I think this happened while the data was implemented. I have no idea how to correct it. This is not the only tease with that problem.

Maybe we could correct the wrong letters with the power of our whole team but then we need a mod mode there

I suggest the guys of Leaseweb should correct that

All my teases have boxes for apostrophes. I fixed one tease but it took a while.

I'm sure it's because I make them in Word then move them over to the editor. If seraph0x say's he can't fix it I'll try to fix the rest of mine through the editor.

Oh yes thats a possibility. Maybe all teases which were created in a text processing program have these mistakes.

That could be. I did my tease inside the editor, and it's just fine.

Regarding the teases, your theory is close, but not quite it. The bug is triggered by the special characters and those editors simply tend to create those.

I'll fix it next week, simply no time right now.

One thing though: Don't fix it on your own. And if you already did please let me know which teases, then I'll exempt them. For the fix to work the charset must be the same for all teases.

jp wrote:All (at least all I've seen so far) of the apostrophes on the forums are also those same boxes. So it's not just the teases.

Hmm, that shouldn't be the case. Do you have an example?

Charsets are quite hard to get right, so bear with me if this takes a bit longer. But we needed to switch to UTF-8 in order to support more languages than just English. The hard drive failure was simply a good opportunity to do that switch.

I see. Thanks, jp!

Actually, it would be a great help if you could all post some of the teases and posts where this problem occurs, just so I have a few examples to work with! Thanks!

http://www.milovana.com/webteases/showt ... =902&p=3#t

http://www.milovana.com/webteases/showt ... =886&p=4#t

http://www.milovana.com/webteases/showt ... =922&p=2#t

Here was used a apostroph but it's spelled right. So the use of an apostroph can't be the only reason.

Working on it now.

dark wrote:Here was used a apostroph but it's spelled right. So the use of an apostroph can't be the only reason.

Apostrophe ≠ apostrophe.

This one is part of the basic ASCII charset and will always work: '
This one is a special char that is making problems at the moment: `

Ok, these should work now thoughout the teases and forums:

’
–
“
”
…

If you have any others that need fixing let me know!

Edit: Fixed that one image as well.

Ok, they should be fixed now though.

jp wrote:I'll let you know if I find any more.

Thanks so much for the help, jp and dark!

The link you just posted works fine for me, so I'm guessing that related to the cell phone issue?

jp wrote:Although, cell phone users are probably a very small market, and it may not be worth spending the time investigating it to get it fixed.

Indeed. The most common mobile platform that users are visiting us with is Symbian (i.e. Nokia) with 933 visits for August so far. That's 0.0% of our traffic.

So no, it's not worth the effort, sorry. Also, it's probably not a problem with our site, but simply the fact that most mobile phones don't support unicode yet. (Here's a test page if you want to find out whether your's does.)

Wow 933, I've never expected so much mobile users