Re: Special Character translation with export help needed

2005-11-08 Thread Boysenberry Payne
I figured out that it wasn't really the special characters that were the issue, but the addslashes function in php with the html tags. I just got rid of the back slashes and all is good. Sorry for the noise... Thanks, Boysenberry boysenberrys.com | habitatlife.com | selfgnosis.com On Nov 8,

Re: Special Character translation with export help needed

2005-11-08 Thread Boysenberry Payne
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 | habitatlife.com | selfgnosis.com On Nov 8, 2005,

Re: Special Character translation with export help needed

2005-11-08 Thread Boysenberry Payne
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 2>&1` and I still get -- MySQL dump 10.9 -- -- Host: localhostDatabase: --

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 ch

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 y