CMS Made Simple Forums

Hi everybody !

Is it possible to have multilingual sites with CMSMS ?

TIA

Kaupolikan

I would also like to know this...

anyone?

I've been thinking about that too... One approach that crossed my mind was to have every page in all desired languages, with the locale code "_en", "_de" etc. postfixed to the alias. So e.g. home_en, home_de, ... The menu plugin would then have to check each item's alias against that of the current page, and show only those items whose aliases match. You'd then place a switch somewhere in the page template to select the language. Downside of this approach is that you'd have all pages in all languages displayed in the pages overview of the admin interface.

If you want to use modules such as ImageGallery, you'd of course have the problem that they only support one template, thus only one language. News however supports multiple templates...

The modifications to the menu plugin should be simple, and the "select language"-function would also be easy to do. Not sure if I missed something here, though...

Yeah, I think in order to do multilingual right, it has to be in the core of the system.  Something where you can select the current language while editing the page.  I have lots of ideas on how to do it, but unfortunatly the priorities are getting the current code base stable first, getting a 1.0 out there, and then going in and ripping a bunch of stuff apart. 

Currently I'm creating a language module which uses a table with menu text and content field where the translated content is saved. The menu text replacement in class.content.inc.php works, but I can't figure out, where exactly the content from table content_properties is given to the content object. I retrieve wrong ids and types ...
Wishy, can you please point to it? 

It's done via a lazy load process in multiple places.  Most notably, in GetPropertyValue, it will check to see if the properties have been loaded, and if not, loads them first before returning the value.

Why does it not work with replacement in content.functions.php in row "$content = $contentobj->Show();"? What is in $content supposed to be?

I am currently working to release a website with content in 3 languages.  I am changing several core files.  I'm passing the language parameter in the URL.  And I had to create extra fields in the content and content_props tables to store translations of content, content name, and menu text.  If anybody wants to help or to get the modified files, email me at katonchik@gmail.com

Hi,

I am very interested in a solution for a multilangural site.

For the moment I am working on a simple solution for this. I need 4-6
different language layers.

I plan to use the existing menu structure in the following way

On the top of the page following menu:
metamenu : Index

Below the metamenu a topmenu depending on the metamenu:
topmenu: >

On the left handside a leftmenu depending on the topmenu:
leftmenu:
>






The solution will probably require that I only use 3 levels in the menu as shown above.

I would be very interested in any ideas on how to realize this. For the moment I am trying pimenu
in combination with some javascript.

Best regards

ok, it's done.  The code is not as graceful as the CMS, but seems to be working.  It's based on 0.11 beta 3.

That is not a problem of the cms , it is a problem of menusystem.

I have made yesterday a very small Website http://czcms.funpic.de  only to show that is no problem to make it with this cms and with pimenu.

The difficult thing making a site multilingual is maintaining the pages. Let's say another page is added in English, then that page must also be added in the German section etc. And if there are different people working with the different translations they must communicate so that each version is up-to-date.

Or quoting the page http://www.cmswiki.com/tiki-index.php?page=Multilingual:

A multilingual CMS needs a workflow system that notifies localizers, perhaps in different countries around the world, of the existence of new pages that must be localized.

A way to easily maintain and coordinate translations
The ideal solution, which I think is what Wishy has in mind for making CMSMS multilingual, is if there are not different menu structures for each language, but where each page can be translated to different languages and with the page in English (or whatever language is default) if the translation of that page to a particular language is not yet available.

That way you can switch to another language on a page without starting from the root level for that language in the menu. And it is much easier to maintain, as the default language and translations are done in the same place (for example a drop-down menu for each page in the admin, where you select what translation to write) and translators could be automatically notified when a default-language page has been edited, added or deleted (and hopefully with a revision system similar to svn, to show what has been edited and what revision has been translated to a particular language).

Careful thinking and a lot of time required
To accomplish this, however, and to make it good and sustainable, requires a lot of careful thinking and especially a lot of work (=time). There is a lot of discussion about this on IRC, so I'm sure that this will be a priority once 1.0 (basically a stable 0.11 with some additions and fixes) has been released. Until then we'll have to cope with temporary solutions, like the ones suggested in this thread.

Pages don't translate themselves
The other thing is of course that it requires a lot of work to translate a site to another language and to keep the translation up-to-date, a page isn't translated by itself. It is then natural that the language that most of the users understand is the language used on the site. Patricia has taken the initiative to coordinate translations of the documentation, which is great! Now I (and whoever else has the calling...) only have to finish the English version...

/Daniel "westis", who is also looking forward to the day when CMSMS has full multilingual support and who only started writing the documentation because there was nothing to translate to Swedish...

Ok Ok - that comes all years later.

The only thing i wish, that this cms get an option select within admin editcontent, to change in content_props  prop_name the value from content_en to content_whatever.

Ok forget my wishes - with pimenu 2.05 i have found a solution for me and other peoples and now i can wait the next years at a solution of the developer team.

Piratos, how do you handle content editing?  You showed only the front end implementation.