Re: [banana123] Quotes and apostrophes do not display wellIn reply to
Mmm, sounds like you are using non-latin versions. For example a ` (thats a latin version, but there is a similar UTF8 version that shows up sometimes as "broken")
Re: [Andy] Quotes and apostrophes do not display wellIn reply to
Hi, I changed it to Unicode. Now apostrophe became a box with a question mark in the middle. For a normal US site, what should be the right character-set?
Re: [banana123] Quotes and apostrophes do not display wellIn reply to
Hi,
Why? If you have phpMyAdmin its VERY simple to convert a table / database into UTF8. Look for it under "Operations". It will most likely be stored as Latin (can't remember the exact name from the top of my head), but you want it as UTF8 (be sure to "convert" it).
Also - make 100% sure you backup all your database as a mysqldump to be sure you have a working copy in case the conversion doesn't work right!
Re: [eupos] Quotes and apostrophes do not display wellIn reply to
With glinks, in most cases, you can tell glinks to be in whatever character set and not touch the database. The only issue with this is that there's a small chance that you'll get incorrect search results and that will only happen if you have multi-byte characters and your search matches one byte of that multi-byte character. The other issue is when you do string operations that need to be mult-byte aware in MySQL and Perl (eg. string length). By default, glinks doesn't do any string operations like that in MySQL or in Perl.
What's important is that the connection character set (ie. how Perl connects to the MySQL) is the same as the database character set. This way no character set conversions happen when the data gets stored by MySQL. With glinks it communicates to MySQL by latin1 and MySQL by default is latin1 (though that might have changed with newer versions of MySQL). Even if we pass in utf8 data, no conversions happen and this is okay as long as when we display it, we tell the browser what character set it is.
One final advantage of doing things this way is that it's fast. We've found that with large sites, utf8 aware Perl and MySQL adds quite a bit of overhead.