MySQL charset converter question

[buildingblocks]

I've change a database from latin1 to utf8 using DrByte's contribution.

http://www.zen-cart.com/index.php?ma...oducts_id=1937

The next step was to modify the configure files and english.php files.

My question:

the readme says

language files (english.php, etc) need define('CHARSET', 'utf-8'); and define('LC_TIME', 'en_US.utf8'); (for english)

I also noticed this section in the includes/languages/english.php file on line 22


@setlocale(LC_TIME, 'en_US.ISO_8859-1');

should that be changed to

@setlocale(LC_TIME, 'en_US.utf8');

[DrByte]

Yes, change all iso-8859-1 to the appropriate utf8 equivalent

ALERT: BE *SURE* TO TEST ON A *COPY* OF YOUR SITE FIRST BEFORE APPLYING THE CHANGES TO YOUR LIVE DATABASE AND PHP FILES!!!!!!!!!!

[buildingblocks]

thank you :-)

[buildingblocks]

All seemed fine until I noticed some product descriptions had been truncated, some having just one character to the description.

I have rolled back to the backup taken prior converting to utf8, so
product descriptions are restored.

Any idea what might cause that to happen to the product descriptions?

[ccn1]

Hey All

If I ran the converter converting Latin1 to UTF8 and did not need it, how can I convert the data back ? Just in case...

Out of interest, what is the actual Charcode and coallition I should be using for UK ?


Thanks in advance
Chris

[DrByte]

If you decide you don't need it, then don't do it.
To go back, the easiest way is to restore from backup.

As for character-set or collation for "UK", whether you're "UK" or anywhere else is largely irrelevant. What's relevant is whether you need to store data from extended characters in your database. And even then, it may not be necessary to use other than latin1 depending on various factors such as whether you choose to complicate things by using PHP files that are encoded differently than the database. If you're not running into problems, then best to not change anything.

[ccn1]

If you decide you don't need it, then don't do it.
To go back, the easiest way is to restore from backup.

As for character-set or collation for "UK", whether you're "UK" or anywhere else is largely irrelevant. What's relevant is whether you need to store data from extended characters in your database. And even then, it may not be necessary to use other than latin1 depending on various factors such as whether you choose to complicate things by using PHP files that are encoded differently than the database. If you're not running into problems, then best to not change anything.

Thanks DrByte

Slightly different now, What if I have ????? - DOH

Can I revert easily ??

{Think I was initially told some wrong info elsewhere}

Cheers
Chris