Internationalization in MODx Revolution

Nope, that is for Evo, probably not even for Evo but for the 0.9.x versions.
The wiki is not official anymore, it is there as an archive...

Excuse me please for dumbness, but I am failing to grasp how all the above could help with "lexicon-less" snippets and date formats.
Regardless of lexicon set $modx->getResouces will output something in the line "Monday, Oct 4 2010".

The dates are out of cultureKey even in the manager (attached). This is not the big deal, but what shall be done with content pages?

setlocale() seems not to be working...

Please, point me in the right direction.

setlocale() should work fine; are you setting this in a plugin or snippet that appears first on every page or what?

Quote from: OpenGeek at Oct 05, 2010, 09:27 AM

setlocale() should work fine; are you setting this in a plugin or snippet that appears first on every page or what?

Thanks for the answer.
Well, I should be more clear in the first place, sorry.
I tried to include setlocale in the index.php, then at the start of the snippet I run. The code is ’setlocale(’LC_ALL’,’ru_RU.utf-8’);’ or just ’LC_TIME’. No effect.

Later I discovered, that in site_content table the dates are integers in the timestamp form, Quip, for example, stores the same as datetime format?

So, basically, I am lost...

As the last resort I may use numeric values and copy and rewrite Quip tpls...

Hi

Have a look at this thread not sure it cover your case but ...
http://modxcms.com/forums/index.php/topic,53991.msg315916.html#msg315916 (sepecially the 3 last posts)

Cheers

Thanks, anso!

I’ll test again on my shared hosting (they run Apache on Unix).