discuss.answer
I think utf8 would be the correct choice.
http://stackoverflow.com/questions/1045338/which-is-the-best-character-encoding-for-japanese-language-for-db-php-and-html
If you do have a mismatch, you should look at this:
http://bobsguides.com/convert-db-utf8.html, but I don't know if the script provided there works on the current version of MODX. Be sure to back up the current DB before doing anything!
Hi,
As I'm based in Hong Kong I deal with Chinese characters a lot and have faced similar problems. As Bob said above everything should be UTF8. (Either utf8_unicode_ci or utf8_general_ci).
If there are collation mismatches you will likely get garbled characters displayed as they won't be stored correctly.
(Actually the best collation to use in the future will be UTF8mb4 as some less common characters require it but MODX doesn't support that yet. I understand it'll be supported in version 3.0!)
I've used Bob's converting script above and it works great.
@Murray - Do you remember which version of MODX you ran it for?
Quote from: BobRay at Dec 12, 2016, 11:00 PM@Murray - Do you remember which version of MODX you ran it for?
Hmm I've used it a few times, probably the latest was version 2.3.x
It shouldn't matter too much though as it's manipulating the database directly rather than via MODX isn't it?
[ed. note: muzzstick last edited this post 9 years, 9 months ago.]
@Carlina - I'm glad I could help. Thanks for reporting back.
@murray -
Hmm I've used it a few times, probably the latest was version 3.x
It shouldn't matter too much though as it's manipulating the database directly rather than via MODX isn't it?
Thanks. It is working on the DB, but the MODX DB has some complicated compound indexes which the script has to manually remove, then put back after the operation, or the script crashes. If new ones get created in a new version of MODX, I have to rewrite the script.
Quote from: BobRay at Dec 13, 2016, 08:30 PM@Carlina - I'm glad I could help. Thanks for reporting back.
@murray - Hmm I've used it a few times, probably the latest was version 3.x
It shouldn't matter too much though as it's manipulating the database directly rather than via MODX isn't it?
Thanks. It is working on the DB, but the MODX DB has some complicated compound indexes which the script has to manually remove, then put back after the operation, or the script crashes. If new ones get created in a new version of MODX, I have to rewrite the script.
Sorry that should have been the latest version I tried it on was 2.3.x (edited)
Ah I see. Thanks I'll keep an eye on that for future versions.