Tiki handles an unilingual website very well.
Goal: To become:
1- a strong tool for multilingual sites (non-parallel and parallel) using version control and document workflow & roles
And then:
2- an open source Translation Management System (TMS) using the Translation Memory eXchange open standard.
Tiki could then easily handle multilingual documentation.
Why do we need all this? Please see the video
UserPagemarclaporte
TikiWiki for a multi language website (January 2nd 2003)
TikiWiki for multilingual site management (May 15th 2003)
Have French/English Tikiwiki Web Site
Open Source:
Typo3's approach
EZ publish's approach
Glasnost's approach
Ovidentia's approach
Wikipedia:Interlanguage links
Wikipedia:Multilingual coordination
This Wikipedia Embassy is being set up as a central place for resources to help with cross-language issues
Localizer with Plone
OpenACS Internationalization
Commercial:
MS-CMS
RedDot
Roxen
Idiom
Discussions:
Xaraya forum discussion on the subject
PHPwiki discussion about Multi Lingual Wiki
Background Info:
3 approaches to Multilingual CM (PDF)
5 Criteria for Selecting a Global CMS
Comparison of MS-CMS and RedDot, includes a section on Multilingual sites, page 4 (PDF)
other links:
Smarty Multilanguage Support
SmartyAndLocalization
SmartestSmartyMultilanguageSupport
best way to build a multi-language site with smarty
Louis Rosenfeled.com: Mar 23, 2004: Multilingual, Multinational Information Architecture Design
reports:
Can content management systems handle your multilingual application needs?
some ideas from gmuslera
[+]An idea to manage multilingual content is to have a table for content strings, something with columns like language and content (probably should be a varchar or something that holds any kind of text content strings in the system).
From there, there are two main directions:
- To replace in all tables the content strings fields with content strings IDs to that database. Maybe for database integrity could be good to have as a column of the content database some reference to where that content come from.
- To put in that new table alternate multilingual content, and to have columns to identify from where it comes from. I.e. a row could be i.e. language->"sp" content->"prueba" table->"tiki_pages" field->"data" id->"TestPage", or something like that. This way actual sites have the content preserved, and for sites that chooses to have multilingual content, before displaying/sending to smarty the content, a search is done in that alternate table for the intended language, the table, field and id to see if a content with that language is available.
Both alternatives are good and can even coexist, in fact, the move could be gradual, after all, the second alternative works with any language, even the default one.