Ok, move thread if location is not appropriate.
I’m working on a multilingual site and have been wondering what kind of system is in the "thought zone" regarding this?
To be honest, my first thoughts of doing this have changed quite a bit and have been thinking that maybe a multi-level approach might be good.
core level
This being the main files of Modx that should have language wordings moved to either an outside file or to the DB.
code level
This being the snippets, chunks, TVs
I was thinking that some of these are going to be langauge specific and others not.
site level
This being the page side of the site.
I’m starting to see the beauty of the system and have grown on Susan’s way of doing things.
Like I mentioned, I’m rethinking my previous ideas, however, I’d like to hear what’s going or start a conversation in regards to what can/could be done.
Codewise ModX is really the cats-pajamas. Thereby, coming up with a multilingual solution I’M POSITIVE ModX is going to go balistic!
Tangent-Warrior

-
☆ A M B ☆
- 24,524 Posts
My solution was a simple one that pretty much just works. I’ve been trying to follow the discussions of multilangauge/internationalization/locale support and it’s still going over my head. So I by no means would hold my method as "the one true way", just a way that I can do it if I have to!
Along these lines, for "international" (non-English) sites I’ve started adding a set_locale(...) call to the config.inc.php file. Makes things like formatting dates (such as for the ditto snippet) much easier.
http://il2.php.net/set_locale