Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2006-08-20 10:54:37
- FireFusion
- Member
- Registered: 2005-05-10
- Posts: 698
Best way to handle a multilanguage site?
We’re looking into converting a big site to Textpattern. This site can be displayed in 5 different languages but we’re wondering how best to do this if we’re moving to Textpattern.
Is anyone else running a multilanguage site in Textpattern?
How did you do it?
Thanks for your help.
Offline
Re: Best way to handle a multilanguage site?
i had just asked a smiliar question and got a negative answer of Mary regarding multilingual feature implementation in txp 4.0.4.
nevertheless, there seems to be plugin development going on:
gbp_l10n
i am looking into this aswell, so see you there.
Last edited by jayrope (2006-08-20 11:17:05)
A hole turned upside down is a dome, when there’s also gravity.
Offline
Re: Best way to handle a multilanguage site?
First of all, it very much depends upon your content and how you organise it. If you have a simple page structure you could set up a section per language and use categories or individual articles as the sub-level. However, if you have a lot of content that is separated into sections and categories it gets complex.
I’ve done that using separate “trees” for each language, i.e. each language version of a page is a separate article. I had duplicate page templates/sections with a language prefix, e.g. en-about-us and de-ueber-uns to which the articles were allocated, with the different page templates restricting the menu choices and UI to the relevant language. In effect it was a normal txp site that was twice or x-times as ‘wide’ (say your normal site has 3 sections, a 2-lang would have 6 sections, a 3-lang 9 sections etc.) and as such had no special intelligence or admin-handling. In the plug-in jayrope mentioned, graeme and net-carver are looking at that kind of thing, both multilingual articles as well as multilingual UI handling but it’s under development at the moment.
I suppose you could also put your language choice into a cookie, then make a more complex page template that shows different menus/UI information (using conditionals) depending upon the language set in the cookie. Then at least you would only need to maintain one set of page templates.
TXP Builders – finely-crafted code, design and txp
Offline