For pcforum.sk, the difference come from the char-set :
- Code: Select all
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
while yours is :
- Code: Select all
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250" />
So I guess that's why.
Anyway, we'll have to perform few test to find out how to deal with this particular set up.
The thing is most of the characters you're listing here should be filtered by this lines of code in includes/functions.php (format_url() ) :
- Code: Select all
$find = "ÀÁÂÃÅàáâãåÒÓÔÕØòóôõøÈÉÊËèéêëÇçÌÍÎÏìíîïÙÚÛùúûÿÑñ";
$replace = "AAAAAaaaaaOOOOOoooooEEEEeeeeCcIIIIiiiiUUUuuuyNn";
The logic is simple, each letter from the $find line will be replaced by the one being at the same position in the $replace line.
As you can see, "à" should already be turned to "a". So we can try to work on several things to fix this.
First on would be if you try to make sure you function.php file is itself using windows-1250, your favorite text editor should be able to find this out and eventually convert it.
Then, if not enough, we would need to check if, but it does not seem like it, some HTML ASCII is not involved and then filter it properly.
Ultimately, if not enough, this would require to use
mb_internal_encoding() and try to set the char-set at the server level as well, as it could as well be the cause for this.
Because for sure, this is all about Char-set.
++