Re: Special Character translation with export help needed

2005-11-08 Thread Boysenberry Payne
, at 3:24 AM, Boysenberry Payne wrote: I tried using `mysqldump $log -v -Q -c --set-charset --default-character-set=utf8 --add-drop-table --add-locks --create-options --disable-keys --extended-insert --lock-tables --quick $db_name -r $bk_file 21` and I still get -- MySQL dump 10.9 -- -- Host

Re: Special Character translation with export help needed

2005-11-08 Thread Boysenberry Payne
, 2005, at 4:57 PM, Boysenberry Payne wrote: Is this the wrong list to ask this on? If so can someone suggest a better list? Am I missing something in my analysis of my problem? Did I not include enough info? Could it be a problem with perl scripts? Thanks, Boysenberry boysenberrys.com

Special Character translation with export help needed

2005-11-07 Thread Boysenberry Payne
I'm having difficulty getting certain special characters to stay the same when I export databases. Here are some of the examples: View of data from phpMyAdmin: Habitat is a “what you see is what you getâ€? or “WYSIWYGâ€? View from table dump via phpMyAdmin export: Habitat is a √¢‚Ǩ≈ìwhat

Re: Special Character translation with export help needed

2005-11-07 Thread Boysenberry Payne
I think the problem is mysqldump uses this: DEFAULT CHARSET=latin1 with --set-charset How can I get it to use utf8? Thanks, Boysenberry boysenberrys.com | habitatlife.com | selfgnosis.com On Nov 7, 2005, at 8:46 PM, Boysenberry Payne wrote: I'm having difficulty getting certain special