You're absolutely right! While the video was only a "proof of concept" with some dates put there just to have something, if people read it, they could have wrong expectation. I'll redo it, hopefully this weekend.

But the one video I'm waiting for is the one from France. It seems like it will be really cool!!!

BTW - XOOPS 3.0 is anticipated sometime in the 1st half of 2009.

We are happy that chco2 is joining our Marketing Team in Netherlands

We need more members, so if you're reading this post and would like to join to be a XOOPS interface to your country, please contact me!!!

We are happy that GPboarder is joining our Documentation Team.

We need more members, so if you're reading this post and would like to join, please contact me!!!

Well, in a perfect solution, we would not only make the content multilingual, but also have a replacement of all the admin "language files", incl. the back-end

As we're offering XOOPS to more people from around the world who might not speak English, it's important that also the back-end is multilingual.

The challenge is to make it a solution where:

- module developers can easily add the Multilingual feature to their modules (like it is done with xLanguage)

- modules owners/admins can easily extract all local text and give it to translator for translations (right done with "language files")

Currently the process is pretty simple and easy. However, it is limited by the need to store everything in one field. So if we could keep the simplicity of the current process, but remove the storage limitation, we would make a lot of people very happy

Quote:
Too bad. We're definitely looking for a better solution addressing multilanguage issues, as the current one where we have to store all translations in one place, and thus run easily out of space, is not satisfactory.

However, your approach might be a good one for modules developers who could follow your steps and create multilingual solution at the module level.

I'll definitely follow your work with great interest, as internationalization of XOOPS is one of my "pet projects"

Just ignore it. Or you can go to the source and comment it out. It's an info to developers with no consequences to you.

OK, I've renamed it and was able to test it!

The verdict is D

Now couple of feedback issues:

* I assume that it was only a test of the backend, as on the frontend I was able to "submit", but there was nothing visible when I went to:
http://localhost/xoops231/modules/newsblack/index.php

Of course, I was able to view/modify the submitted content from the Admin menu

* If I remember correctly, you've mentioned couple of months ago that this solution would allow to store each language files separately, thus we would never run into a problem with not sufficient space for the title, if we have a long title and more than two languages as it is right now. Therefore I think this would be a very useful feature.

* But it would be the most useful feature if it would be part of the core, i.e. we would make the core multilingual with xLanguage and your solution, and then every module could could tap to it and define each its field as multi-lingual.

* The next question will be how to make an easy translation of the content, i.e. if you release it in English, how could people add more languages in a very easy way. The "lang_tool" has a good concept for it - you might take a look into it.

In general, whatever will help us to get away from field size and number of languages limitation, is a very good thing!

So I very much appreciate your efforts!!!

Can you rename it to something different? Having it as /news would overwrite my installations of Herve's News module, and I cannot do it.

JahArt Studio published its list of CMS TOP 40 of 2008.

We were very pleased to see that XOOPS was listed as #6.

See: here

Thank you!

I was going to do it, but never got to it due to the 3.2.2 situation