1
Hello all,
XOOPS looks like one of the very cleanest solutions in the PHP CMS world. I want to construct a serious portal / community site for researchers in a particular field, and the site has to be bilingual -- i.e. users have to be able to change the language of at least all the interface elements on the fly (this is very easy with PostNuke). The lack of real support for multilingual sites seems to be one of the few major weaknesses of XOOPS.
So I'm wondering what solutions exist to this problem, as I'd really like to use XOOPS.
1. The good people who created the Multilanguages hack have quite responsibly filled it with disclaimers... I'm wondering if, in the educated opinion of experienced XOOPS users/developers, anyone can recommend using this hack on a serious production site that a lot of people will be relying on?
2. Are there plans to include true multilingual support in the XOOPS core (in the near future), or is this not a priority?
3. Are there any other practical solutions, e.g. some kind of multisites set-up?
I would be very grateful if anyone could help me out with this. And congratulations on building a great product and a supportive community!