Re: Encoding problem...

[Ted Ashton]

Hi,

Some more informations.


The dumped file contains other table etc, but this is the one pertinent to the above two examples:

DROP TABLE IF EXISTS `pages`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `pages` (
`page_id` int(11) NOT NULL AUTO_INCREMENT,
`parent` int(11) NOT NULL DEFAULT '0',
`root_parent` int(11) NOT NULL DEFAULT '0',
`level` int(11) NOT NULL DEFAULT '0',
`link` text NOT NULL,
`target` varchar(7) NOT NULL DEFAULT '',
`page_title` varchar(255) NOT NULL DEFAULT '',
`menu_title` varchar(255) NOT NULL DEFAULT '',
`description` text NOT NULL,
`keywords` text NOT NULL,
`page_trail` text NOT NULL,
`template` varchar(255) NOT NULL DEFAULT '',
`visibility` varchar(255) NOT NULL DEFAULT '',
`position` int(11) NOT NULL DEFAULT '0',
`menu` int(11) NOT NULL DEFAULT '0',
`language` varchar(5) NOT NULL DEFAULT '',
`searching` int(11) NOT NULL DEFAULT '0',
`admin_groups` text NOT NULL,
`admin_users` text NOT NULL,
`viewing_groups` text NOT NULL,
`viewing_users` text NOT NULL,
`modified_when` int(11) NOT NULL DEFAULT '0',
`modified_by` int(11) NOT NULL DEFAULT '0',
PRIMARY KEY (`page_id`)
) ENGINE=MyISAM AUTO_INCREMENT=445 DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;

If I view the dumped .sql file in my browser with UTF8 encoding, 'ç' is displayed as a 'ç'; if I view it using 'latin 1' encoding, 'ç' is displayed as 'ç'. Does this mean it 2 bytes in the dump?

Cheers,

Chris