By Alexandr-1 on

Is there way to make terms multilangual?
I going to use i18n.module for content translations but i also planing to use taxonomy_dhtml so i need vocabulary terms to be multilangual. Is this possible?
Thank, Alexandr.

Comments

matteo’s picture

matteo commented

I'm putting into production a website with multilingual taxonomy.
I modified the standard taxonomy module in order to have such feature.
This module is based on pre-4.4 release, and in these days I'll migrate it to 4.4.
You can have a look at www.matteoferrari.org and see it into action.
It is a preview of my Cantincoro site, a portal on choral music.
It also contsains a modified taxonomy_html module which integrates my modified taxonomy.

If you're interested in the module, I can send it to your e-mail (unfortunately the version on my sandbox (my user is matteo) is old.

Matteo

hamlet’s picture

hamlet commented

I'd love to have it too!
Please send modules you changed to me at etern [@] list.ru
Or maybe it's better to lay'em into sandbox?
Thanks!

matteo’s picture

matteo commented

Ok, my friends, I put the modules into my sandbox (http://cvs.drupal.org/viewcvs/contributions/sandbox/matteo/modules/Drupa...)

You can try them, but keep in mind:
- they are 4.4 compatible, but I need to migrate them to 4.4 (help accepted)
- taxonomy management is not integrated; this means that every time you add/remove/change vocabularies or terms you must update your localization by hand (this is an open point; I'm waiting to know what will go on with 4.5 to work on it)

Feedbacks are well accepted; I'm insisting on this feature because it would immensely help creating multilingual sites !!

You'll find also a prototype of taxo_search.module, a taxonomy search modulke based on taxonomy_html, but it is not finished...

Please let me know about your experiments....

Matteo
mailto:webmaster@cantincoro.org

Alexandr-1’s picture

Alexandr-1 commented

Thanks, Matteo.
But i cant switch languages at your site.

matteo’s picture

matteo commented

OOps, I fixed the problem.
The fact is that page caching inhibits translation.
Consider I'm not expert on Drupal core, so my solution is not as complete as i18n (I'll try it very soon).
I also put on my sandbox a new directory where set_lang.js and a modified version of common.inc (hacked to support locale cooike) are.
You must use it together with taxonomy.
Now you can also retry on my site. It now works !!

I also hope that in some way there will be native support on 4.5...

CIAO
Matteo
mailto:webmaster@cantincoro.org

Alexandr-1’s picture

Alexandr-1 commented

Yes, this works now! but i think i will try i18n.module (already trying to work with).
Module not complete but look's like this module is the best solution for multilanguage provided now.
Thank to Jose A Reyero!
May be you consider to use i18n too.

matteo’s picture

matteo commented

Yes, I think I'll consider i18n too, but I would like to undestrand if it will become a native function or not...

Matteo
mailto:webmaster@cantincoro.org

Jalal’s picture

Jalal commented

I am a newbie. I have been looking into this forum and read most of the posts and all instruction on i18 and localisation but I just do not understand what is the simplest way of doing the content translation. Could you help me in a few steps what do I need to do to add French content to my Drupal 4.4 English Site.
Thanx

jose reyero’s picture

jose reyero commented

I am updating the i18n.module to support *real* content translation for *any* table you want.

The current HEAD version in CVS does support it, though it might be not in the tar.gz package yet (?). You just have to add *all* the taxonomy tables to the list in config file, take a look at the SETUP and README files.

There's also some node synchronization between languages and there will be also soon taxonomy synchronization, currently testing it..

Notice that currently it is an experimental feature -and only for Drupal>=4.4 -, so not ready yet for production sites, but I will be polishing it for upcoming versions.

https://reyero.net

Alexandr-1’s picture

Alexandr-1 commented

Don't know where I need to post bug reports about i18n posting there.

Something wrong with data duplication.
I setup last version (1.4) of i18n module.
When I create vocabulare in Russian language module duplicates it for English language but something wrong with node type. For Russian I set selects 'page' node type and this sets ok in database but duplicated node has EMTPY node type when I browsing 'vocabulares page' on English.

Alexandr.

jose reyero’s picture

jose reyero commented

The name of the project is Internationalization and you can post a bug for that project. -Maybe it's a but confusing having module name != project name, I'll think about it

I'll take a look at it anyway, but please, create a bug so we can keep track of it...

https://reyero.net

Alexandr-1’s picture

Alexandr-1 commented

Don't know where I need to post bug reports about i18n posting there.

Something wrong with data duplication.
I setup last version (1.5) of i18n module.
When I create vocabulare in Russian language module duplicates it for English language but something wrong with node type. For Russian I set selects 'page' node type and this sets ok in database but duplicated node has EMTPY node type when I browsing 'vocabulares page' on English.

Alexandr.

joel_guesclin’s picture

joel_guesclin commented

I have tried using i18n on CVS 4.4-RC a while back, and liked the look but unfortunately could not get it to work how I wanted - so I am very keen to try out the new version.

But, I would like to know: will it support only content translation? Consider these two use cases:

1) I want to have the same content in two languages. So I create two pages (called "subscription" for example) and i18n allows me to switch between www.mysite.com/en/subscription and www.mysite.com/fr/subscription. Ok, this is good, I have done this with i18n and it works.

2) But my site also has content which is unique to each language. So for example, if I am looking at www.mysite.com/en/gardening/flowers there is no French equivalent, because my French site only has stuff about cooking. If I change languages at this point I want to return not to www.mysite.com/en/gardening/flowers but to www.mysite.com/fr (the French home page).

Will i18n allow me to do this?

My other thought, is that to keep the different languages' content really separate it ought to be in different tables and i18n should then play with the table prefix - but I don't know enough about Drupal to know if this would work like that.

JG

jose reyero’s picture

jose reyero commented

Yes, the latest version -cvs- does support content translation -still experimental- and content is stored in different tables for each language. Actually, it already supports 'any table' translation throuch table prefixing -check the README and the INSTALL files...

Currently, when you create a new node it creates/deletes a new node or taxonomy term for each language, which is supposed to be translated later manually. Same for taxonomy. For now, you can mark the nodes in other languages as 'unpublished'.

If you are using only multi-language with custom URLs, you can also create custom urls without language prefix, 'gardening' The module searches for the requested path 'en/gardening' and if not found, defaults to the same page without language prefix 'gardening', at least not presenting the 'page not found' message... Does this help?

And you can configure in Drupal -standard- the page to be presented as 'page not found', and I think you want to set it to the homepage -node-. I will think about making it also language-dependant...

I'm sorry I can't give you a clear answer right now, but I am redesigning the module to support multi-language-multi-table-multi-everything and I'm just thinking about how to make it all fit, specially the synchronization between languages.

I will add this to my list of requirements, just can't tell you *when* it will be supported, maybe in upcoming versions...:

x.x. Configurable and language dependent 'page not found'

https://reyero.net

joel_guesclin’s picture

joel_guesclin commented

I've looked at the readme and install in the latest version of i18n that I just downloaded, but I can't find anything about table-prefixing. Please could you be more explicit about this? Should I create different node tables and taxonomy tables for each language I want to support? Exactly which tables do I have to create for each language? Do I have to change anything in the other modules or does i18n take care of everything?

Good luck for the "production" version - very exciting!

jose reyero’s picture

jose reyero commented

I've checked and it was already there I think it takes up to 24 hours till the changes get packaged into the tar.gz file.

I will be committing a more stable version, with some changes and new features in the next weeks. Though configuration options may be slightly different, the table structure for multiple languages will be the same.

The multitable option is expected to work for any module/table without patching, and the node synchronization will work for most of them.
About which tables you have to duplicate, it will depend on what you want to achieve. I'm working out myself the effects duplicating some tables has, so sorry, I can´t give you a list right now. Only some clues:

Suggested tables to be made language dependent are:
- For nodes:
node
node_term
*also related node tables for each node type
- For taxonomy
vocabulary
term_data
term_hierarchy
term_synonim
- For comments
comments

If you want to experiment with different tables, you may find this useful [Drupal ERD]:

http://lists.drupal.org/pipermail/drupal-support/attachments/20030530/7a...

Let me know about your experiments!

https://reyero.net

Alexandr-1’s picture

Alexandr-1 commented

Good day, Jose A Reyero!
I'm find i18n module useful for creating multilangual content. But there some problem.
For example when i changing node wight for one language then there is no changes for other.
May be some features like data synchonization will be useful in this case?
For example 'i18n.module' administration interface may have input to setup tables and fields which i want to synchronize.
In this case users can setup weight, path mask, and other no language dependant info for one language, then go to i18n control panel and synchronize other languages to edited one.
I think this feature will be good usability improvement for your great module.
Thanks!

joel_guesclin’s picture

joel_guesclin commented

I've made some first attempts, very very simple, to set up a site in French and English. I think I may not have properly understood how to set up the default in includes.conf, because I tried setting up tables en_node and fr_node, and setting the default to "en" - but it still ended up looking for just plain "node" when I go to the first front page, and complaining because it couldn't find it.

However, I did seem to manage to set up both French and English vocabulary so that creating a Vocabulary in English would also create the same vocabulary in French. Trouble is, when I go to translate the vocabulary into French, it also translates it in the English version.

What did I do wrong?