The new hosting uses MySQL - 4.0.27 , my previous hosting uses MySQL - 4.1.21, so before uploading the database to the new hosting I exported it degraded to a 4.0 compatibility via phpMyAdmin. Then I uploaded it via phpMyAdmin to the new hosting.
Checking via phpMyAdmin I do see the new database with the spanish characters correctly at the new server, but the site is presenting the spanish characters not correctly.
The only way I've run into it is uploading backup files with the wrong character set, but that would show up in phpmyadmin. WSN shouldn't alter what the field says in phpmyadmin, unless perhaps you have the WSN character set set wrong.
The phpMyAdmin of this hosting does not have the capability of selecting the "Character set of the file" to import. Also as they are using MySql 4.0.27 , the instructions as "CHARSET=latin1" can not be included in the MySQL database. When not having any character set specified on the meta instructions, the spanish characters from the database are presented wrong, but the spanish characters directly written on the templates and the ones from LANG_ variables are presented correctly. By the contrary, when adding: <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> the spanish characters presented from the database are shown correctly, but the spanish characters written directly on the templates and the ones form the LANG_ variables are presented wrong.
As for more information, at my previous host, when stating: <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> all the spanish characters were presented incorrectly, but simply deleting this meta instruction all spanish characters were presented correctly.
Just to comment, in case it can be of use for others, the MySql charset of my previous host was UTF-8 Unicode (utf8) by default. The only way I found to change it was to open the database on TexPad (preconfigured to read the document as utf-8) and to save this document with ANSI encoding.
Now I can state at Language, the charset to be latin1 without any problem.
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on spanish characters changed
Forum Regular
Usergroup: Customer
Joined: Aug 09, 2004
Location: Chile
Total Topics: 172
Total Comments: 462
After new hosting migration all spanish characters are not presented correctly at my site. An ó is presented as a ó an à is presented as à an é is presented as é .
The new hosting uses MySQL - 4.0.27 , my previous hosting uses MySQL - 4.1.21, so before uploading the database to the new hosting I exported it degraded to a 4.0 compatibility via phpMyAdmin. Then I uploaded it via phpMyAdmin to the new hosting.
Checking via phpMyAdmin I do see the new database with the spanish characters correctly at the new server, but the site is presenting the spanish characters not correctly.
What can be the cause of the problem ?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The only way I've run into it is uploading backup files with the wrong character set, but that would show up in phpmyadmin. WSN shouldn't alter what the field says in phpmyadmin, unless perhaps you have the WSN character set set wrong.
Forum Regular
Usergroup: Customer
Joined: Aug 09, 2004
Location: Chile
Total Topics: 172
Total Comments: 462
The phpMyAdmin of this hosting does not have the capability of selecting the "Character set of the file" to import. Also as they are using MySql 4.0.27 , the instructions as "CHARSET=latin1" can not be included in the MySQL database.
When not having any character set specified on the meta instructions,
the spanish characters from the database are presented wrong, but the spanish characters directly written on the templates and the ones from LANG_ variables are presented correctly.
By the contrary, when adding:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
the spanish characters presented from the database are shown correctly, but the spanish characters written directly on the templates and the ones form the LANG_ variables are presented wrong.
As for more information, at my previous host, when stating:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
all the spanish characters were presented incorrectly, but simply deleting this meta instruction all spanish characters were presented correctly.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Don't use utf-8 for non-utf-8 languages. Spanish is latin1. Admin -> Customizations -> Languages -> search for the item named charset.
Forum Regular
Usergroup: Customer
Joined: Aug 09, 2004
Location: Chile
Total Topics: 172
Total Comments: 462
Thanks for the help.
Just to comment, in case it can be of use for others,
the MySql charset of my previous host was UTF-8 Unicode (utf8) by default. The only way I found to change it was to open the database on TexPad (preconfigured to read the document as utf-8) and to save this document with ANSI encoding.
Now I can state at Language, the charset to be latin1 without any problem.