1
Dear friends,
For years I'm using CMSs in my work and since the beginning XOOPS is my favorite.
Here in Brasil the situation of XOOPS is not very comfortable, there are several abandoned sites, outdated, careless and causing confusion and bad impression on the XOOPS users. Recently we lost our only stronghold of translation of the modules and the Core with the closing of
http://www.XOOPS.org (for personal reasons of the administrator).
I do not think the communities who speak Portuguese deserve to be deprived of using the XOOPS in their native language, but instead of starting another domain asking for volunteers to translate, I would suggest here that the translations in xoops.org should be centralized.
I'm a member of the Fedora Project for many years, including the translation team, and from experience I see that a centralized system of translation works very well.
What I think is the following:
* xoops.org gathers and provides the modules using a version control system.
* Translation teams may have access to all modules in one place, translate them and send back (always in UTF-8) the folder language
* xoops.org adds the translations to the module.
I step up to ask for volunteers to the translation team to Portuguese, and at last, I think much easier if in the future XOOPS adopt the pot files to facilitate internationalization.
Regards
