I'm looking for multilingual language functions including two levels.
1. UI level:
on clicking on drop-down menu, the user interface will reload and change into the target language.

2. database level:
a module that is able to cut in the data rendering from database of a language before presentation, so after the module users are able to see the data in target language.
this might be difficult to achieve. if it provides a compensation by inputting corresponding "key words" in other languages to echo to some data in base language (which is difficult to translate) in the database, it is still acceptable.

Highly appreciated if anyone could help.

Comments

drupalnesia’s picture

Try i18n.module
I have use this module and found that everything work fine. You just need to create a select list which targeting to specific language, i.e: for English www.domainname.com/en, while Indonesian is: www.domainname.com/id.

Since this module already have Language Swicther box in list format then easier to change to select list format.

WJ’s picture

1. UI level:
2. database level:
a module that is able to cut in the data stream in base language from database before presentation, so after the module rendering translated data users are able to see the data in target language.
this might be difficult to achieve. if it provides a compensation function by inputting corresponding "translated words" in other languages to echo to some data in base language (which is difficult to translate) in the database, it is still acceptable.

Most translate modules work on UI level. I have not found any working from database level.

Can i18n translate from database level?
Or, if there are any multilingual modules can translate database?

drupalnesia’s picture

GiorgosK’s picture

But Localizer has a nice feel to it too, its worth a try at least.

One things I really need to know if anybody has enough knowledge, which directions is the drupal core going to go
I18n or Localizer ? is it going to be in the core? why don't this two modules join forces ?

Thanks
----
world experts tag cloud

------
GiorgosK
Web Development

WJ’s picture

As a newcomer, I can find i18n in Wikipedia, but not localizer. Could kongeo and anyone please help explain the differences?

From my surface observation, I think the translation can be done in two ways: all content being translated at server end or at client end.

Translation at server end may consume some overhead in terms of server resources. Users at client end can read target languages in web pages after making their selections.

Translation at client end may demand downloading a translation plug-in of desired language so as to translate web page content into desired target language (is it localizer? it's like Firefox' FoxLingo, isn't it?).

Maybe my perception is quite rough or bias. I would be appreciated for any further inputs.

GiorgosK’s picture

I chose Localizer because I see it cooperates well with the modules I want to also have enabled

try both with your own setup (enabled modules and contributed modules) and see which one behaves better
but, have in mind that one, or the other or a derivative of the two will probably be in core soon (hopefully by version 6)

also remember that you cannot have both of them enabled at the same time

----
world experts tag cloud

------
GiorgosK
Web Development

WJ’s picture

Thanks a lot for further inputs.

By the way, what is the difference between enabled modules and contributed modules?

Also, there is a post by Florian in http://drupal.org/node/88417 regarding multi-site approach to do multi-languages. It demonstrates a website in two languages by http://streight.co.uk and http://streight.co.uk/ro/. It looks like making two databases for two languages to me.

Because some professional terms, like nodes, are difficult to me, how do you feel this multi-site approach compared with localizer and i18n?

Thanks.

GiorgosK’s picture

I meant "core modules" (that come prepackaged with drupal)
and "contributed modules" (that are contributed by drupal community) and have to be downloaded (http://drupal.org/project/Modules/name) seperatelly and enabled and may or may not work properly with the core installation and the rest of the contributed modules.

Localizer and I18n are two contributed modules (very activelly developed) trying to help out anybody who wants to build Drupal sites with Multilingual capabilities.

I can't offer any great insight on which one is best for you but I suggest you install drupal on your own server and try both localizer and I18n. See which one fits your needs best, make sure you report any bugs that you encounter so the developers can get rid of them (thus making them better).

----
world experts tag cloud

------
GiorgosK
Web Development

drupalnesia’s picture

For detail please visit:
http://groups.drupal.org/i18n

Defining a roadmap for i18n in Drupal 6 core, here: http://groups.drupal.org/node/1967