Issue if MOD'x encoding is set to UTF-8, and WLPE database is set to latin?

☆ A M B ☆
24,524 Posts

sottwell Reply #21, 18 years, 7 months ago

The setting in the MODx configuration is used for the character set of the web pages sent out (header information). Noting to do with the database. That’s why you can get validation errors if you have MODx configured to one character set and have a different one specified in the head of your template.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

4,205 Posts

dev_cw Reply #22, 18 years, 7 months ago

Quote from: sottwell at Feb 20, 2008, 02:23 PM

The setting in the MODx configuration is used for the character set of the web pages sent out (header information). Noting to do with the database. That’s why you can get validation errors if you have MODx configured to one character set and have a different one specified in the head of your template.

That is what I meant to say, realy grin

[font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

Something is happening here, but you don't know what it is.
Do you, Mr. Jones? - [bob dylan]

☆ A M B ☆
24,524 Posts

sottwell Reply #23, 18 years, 7 months ago

That’s ok, it gives me a headache just trying to keep it all straight. Database, database client, connection, HTTP headers, gah. Why doesn’t the whole world just give it up and go for one language? Russian, Chinese, Farsi, Swahili...just pick one and go with it. It would solve so many problems! There is absolutely nothing inherently "superior" in one language over any other. Or maybe I’m just a little disgruntled because after 10-12 years I still can’t speak Hebrew very well grin

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

24,544 Posts

BobRay Reply #24, 18 years, 7 months ago

Quote from: sottwell at Feb 20, 2008, 03:08 PM

That’s ok, it gives me a headache just trying to keep it all straight. Database, database client, connection, HTTP headers, gah. Why doesn’t the whole world just give it up and go for one language? Russian, Chinese, Farsi, Swahili...just pick one and go with it.

Or at least one universal giant character set. Even UTF-8 won’t cover all the languages. :’(

Bob

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

925 Posts

Soshite Reply #25, 18 years, 7 months ago

Quote from: sottwell at Feb 20, 2008, 02:08 PM

The exact content of that line is important. It has to be in a specific form or it won’t work.

http://dev.mysql.com/doc/refman/5.1/en/charset-unicode.html

$database_connection_charset = 'utf8';

(My host uses PHP 5.1.4 and MySQL 4.1.15, if that helps any. If this might be a PHP issue, I can give someone my PHP info data from the MODx Manager.)

And man is all this stuff confusing. At least, if anything, I’ve learned about all this charset stuff. tongue

My Snippets
-> PopUpChunk v1.0

MODX Staff
10,725 Posts

opengeek Reply #26, 18 years, 7 months ago

If your db content is latin1, you likely need to be using latin1 for the database_connection_charset and ISO-8859-1 or ISO-8859-2 as the charset rendered by your pages/PHP headers. Presenting latin1 db content as UTF-8 is the problem, plain and simple, and converting it, if you are already using latin1 characters that do not have utf8 equivalents, converting it from one to the other is not so plain and simple.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

925 Posts

Soshite Reply #27, 18 years, 7 months ago

Quote from: OpenGeek at Feb 20, 2008, 05:17 PM

If your db content is latin1, you likely need to be using latin1 for the database_connection_charset and ISO-8859-1 or ISO-8859-2 as the charset rendered by your pages/PHP headers. Presenting latin1 db content as UTF-8 is the problem, plain and simple, and converting it, if you are already using latin1 characters that do not have utf8 equivalents, converting it from one to the other is not so plain and simple.

Okay, so now that I have the line in config.inc.php changed to latin1, and Western European (ISO) - iso-8559-1 selected in the Manager, I should be "good to go" to test to see if the issue resolved itself?

(And try Central European (ISO) - iso-8859-2 if that doesn’t work, just in case?)

UPDATE: Doing a quick check w/ the first option, it gave the same error. Just to check, if the "overall" charset for the database as a whole is set to UTF-8, does that affect anything, or does the latin1 setting override that in MDOx?

My Snippets
-> PopUpChunk v1.0

MODX Staff
10,725 Posts

opengeek Reply #28, 18 years, 7 months ago

It’s really simple:

want to present html in UTF-8; use utf8_ collations in the db
want to present html in ISO-8859-1; use latin1_ collations in the db

have a utf8_ collation in the db already; present with UTF-8
have a latin1_ collation in the db already; present with ISO-8859-1

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

925 Posts

Soshite Reply #29, 18 years, 7 months ago

Everything set as you said, and I made sure the tables were emptied, so this must be a issue with the site configuration then, right?

So now that we’ve figured that out --- would anyone be willing to look at my site’s PHP info and try to debug what’s causing the issue?

My Snippets
-> PopUpChunk v1.0

958 Posts

motsmart Reply #30, 18 years, 7 months ago

There is nothing more related to the character rendering as Jason mentioned, So i guess there is only a tiny little mistake that causes the problem!, I personally confuse sometimes when i change the keyboard config b/w languages i have installed, So in which language is your user/pass or how many language do you assign to the keyboard config?, Make sure everything is right in each case before you switch a db settings.

latin assigned/connected db should parse okay in English but for any double-byte languages -say Japanese, Chinese... you better use utf8 assigned/connected db.

@ Susan & Bob
Better not to forget that computers are still stupidest even if you teach’em they can’t learn!, They do what you (as humans) have given’em before!, So its our issues if they make mistakes, Not an elegance of living in a world which have cultural or fundamental changes like Languages, Skin colors, etc... .

[img]http://i10.tinypic.com/52c4eir.gif[/img][/td]
[td][Wiki] [Persian support forum]
[SVN] [RTL SVN Branch] [bugs] [FishEye+Crucible] [Learn MODx!] | [My Google Code]
[font=tahoma][برای دسترسی به راهنمای فارسی به [url=http://www.modxcms.ir]