History: MultilingualWikiPage

The discussion began with the page :
French forum
and
MultilingualDev

What do we want?

• by default, a user sees the page in his language when it exists otherwise the page is displayed in the original language (the page creation language).
• a user can see all the languages where a translation is available for the page when he displays this page (sylvie: I think it must be marked with the language name not the country flag)
• a user can see a page in another language that is not his language, even if the page exists in his language
• the language of an existing page is necessarly defined at the first translation to another languague.

• the page name is the same between all the language:
  • otherwise, pages linked to the page will be tricky!
  • a page name change will be tricky!)
  
  Comment by Chealer : why? The main use of WikiWords is that it can fit in an understandable text, else you'd always use the ((pagename|description)) syntax. For certain pagenames like I18nDev it's fine, for all other it doesn't work. It's IMHO better to use a default pagename for all languages and allow each language to change it's own. This way, a languageY page will link to a languageY page automatically. It's true that the linguistic problem will require a big DB change, but well...this is a problem!
• if a page is deleted (whatever the language is), all the translated page are deleted (otherwise what will be the default language?)
• a translated page has its own history, author.... (probably mixed somehow with the one of the "source language", in the situation that will occur most of the time with a centralized page maintainer and translators-Chealer9)
• last pages applied to the translated pages

• Soron_12F proposes to organize the page translations with Galaxia

IMO, since Wiki isn't the only part of Tiki, we'll need some more user preferences
I guess the user should rate each language ;
By example, in my case I'd use (supposing the rating is on 5) :
French 5
Ido 5 (you don't know this one eh😛 )
English 4
[...] (those points are for those who really know more than me!)
All other languages 0

Admin should probably have an option to set his Tiki as multilingual or not
Chealer9

• Monitoring : do we have to choose the languages to monitor? I guess so 😕
  In this case we can probably rely on user's linguistic preferences
• RSS feeds : as above (anyway we can rely on the way other programs behave...who knows this behavior?)
• Templates : different templates 😑
• Modify : new checkbox/radio box : linguistic modification/content modification
• Comments : probably show the comments using linguistic preferences too?
• Attachments : Seems we have to give an option for translated attachments too, eh?😐

Chealer9

It seems a multilingual environment needs as much modifications as WYSIWYCA... we have some kind of What You See Is What You Can Understand here. So, implementing all this stuff (plus for other features!!) can justify a major version (will it be 2.0?), or more realistically, this implementation will be gradual.
Also, the content of this page really fits in the discussion part of MultilingualDev. I think the multilingual problem needs to be considered as a whole because of the multiple interactions in Tiki.
Chealer9

Feel free to update - comment the page