Hi.
I've spent many days to create a new module for Drupal content translation,
to add support for multiple languages to Drupal websites.
I've started with a new module because I have found a lot of difficulties in
using Internationalization module.
In every case, many features can be implemented in a separate module,
but not all, regardless of which approach you select.
Some patches to the core are necessary to make Drupal useful and complete
in a multilanguage environment.
If you want to add language prefix in the url : it/home, en/home,
for example, a lot of problems appears from menu module.
I've written some patches also for this, but it isn't a good solution.
To add content support to blog, node and taxonomy, patching seems
to me the only viable option.
Also the poll module could be translable only with locale module.
I think that adding patches cannot be a long term solution.
My proposal is to integrate content localization directly in the core.
The starting point could be the locale module, to translate only the strings,
and then using an additional module to translate the content.
I think that we have already a lot of code available from Internationalization
and Localizer module. So, I think that the most work would be already done.
Let me know what do you think and what can be done.
Thanks
Roberto
Comments
Comment #1
killes@www.drop.org commentednew features go into devel version.
Comment #2
coreb commentedmoving from x.y.z to 6.x-dev version queue
Comment #3
pasqualleComment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.