By danny_joris on

Hi all,

I have a multilingual website with 2 languages and a content type called 'Product'. If I want to translate it from one language to another, I have to make a new node. Very convenient in some cases, but not mine in this project. I only need to translate the description. This is to list wines.

What needs to be translated:
-description

What needs to remain the same:
-title
-pathauto url based on title
-cck number: Price
-cck date: Year
-image

I know you can remain all this information with a second node, I'm just thinking that the client will need to update the price for a certain year because they get more expensive per year. I'm imagining that the client will need to change the price twice per product and that could be a hassle.

Isn't there a way to make a new node that needs to be filled out only once and that contains two description fields: one for each language.

If this solution does not exist, I will make it a feature request.

Cheers,
Danny

⋅ Categories: Drupal 6.x

Comments

danny_joris’s picture

danny_joris commented

any ideas?

pkej’s picture

pkej commented

there is a module for it, but i can't remember the name. perhaps i18n filter? check out the multilingual modules and filter for 6.x and try searching for "input filter"

Paul K Egell-Johnsen

pkej’s picture

pkej commented

1. The module i was thinking of let you tag the content for each language in one text area using input filters

2. There is another module which claims to do what you want. toghether w i18n sync it might create two synced nodes as god intended :p

b/c i'm on an ipod i can't be bothered to look up the modules for you

Paul K Egell-Johnsen

danny_joris’s picture

danny_joris commented

Hey Pkej,

Thank you very much to share your ideas. And a special appreciation bonus for using your iPod to do this. :)

I kinda found what I'm looking for in this module: http://drupal.org/project/ipetranslation

You can make translation nodes in one form. You can choose per content-type what fields should be translated. For example I only wanted my 'body'-field (description) translated, so when I create new content there will be 3 body fields in the form. One Dutch, one English and one French. The other fields (in my case: title, image, year, price, etc) will be used for all 3 nodes that will be created after submitting this form.

The only thing that I would love to see different is that when you go back and edit the dutch translation (for example) and change the Price or Year, that this is only submitted to the Dutch node translation. It would be great if you change the Price or Year, that the other nodes would change that too. Just like the initial creation form does. That way if my client wants to update his price or years, he doesn't need to update 3 nodes. I'll make an feature request for this later and when I do, I'll post a link to it here.

Thanks again for your help, Pkey.
Have a great weekend,
Danny

pkej’s picture

pkej commented

The one I meant in 2. was the one you found.

Using i18nsync you can tell, on a per node basis via the content type forms, which cck fields to synchronize, and other fields, like image (as a very relevant example, latest dev of image and i18n needed.

However, the module I was referring to in 1. above is the Language sections module. It seems to simplify what you want, especially since you have a limited number of languages; and because i18n + i18nsync + image didn't work until recently for 6.x; they worked in 5.x, but it has taken a _couple of years_ before they have started working on 6.x.

As for image vs imagefield; the reason I stick with the former is image browser, image assist and similar plug-ins for wysiwyg editors; they all seem to like images not imagefields.

Paul K Egell-Johnsen

pkej’s picture

pkej commented

Because you can use multilanguage menus and taxonomies. I suggest looking into http://drupal.org/project/translation_table as well, as it will simplify the synchronization of menus and taxonomies with your content.

Paul K Egell-Johnsen

danny_joris’s picture

danny_joris commented

Thanks very much for your help, Paul.

The only thing that I would love to see different is that when you go back and edit the dutch translation (for example) and change the Price or Year, that this is only submitted to the Dutch node translation. It would be great if you change the Price or Year, that the other nodes would change that too. Just like the initial creation form does. That way if my client wants to update his price or years, he doesn't need to update 3 nodes.

In the meanwhile I found what I was looking for. I don't know what module gives this option, but I found the synchronize translations option in the edit content type form. I can't believe I've overlooked that the entire time. This solves my problem completely.
http://dannyjoris.be/files/fora/Synchronize_Translations.png

Cheers,
Danny