I have had to create a new vucabulary (on economic activities codes) and its taxonomy terms in a batch process. I easly did it thanks the feeds module ...
Each term has it's descriprion field that might obviously (and should ...) e translated in english and spanish.
The Feeds module was unable to correctly accomplish this, although its mapping system seems to allow special fields content to be destinated to specific language versions. It didn't work for me ...

I attach the table version (excel file) of the vucabulary structure I would migrate in drupal as a vucabulary ...
(as you can see the second and the third field are the english and spanish version of the description field I would reproduce). The code filed is the unique identifier and title of the terms.

When I map the eng_description and esp_description fields to the term description, assigning them to different languages, the version created of the description for any term is the latter I map in the list, and this is assigned to every language of the drupal site (so means no localization at all).

Is this a missfunction of the Feeds module??, that might accomplish this, instead ??
Any hope in some future fix???

Thanks for any help ...

An hopeful thanks (really hopeful) for any help ...

CommentFileSizeAuthor
#4 vucabulary_to_be_translated_0-1.xls18 KBrichar
vucabulary_to_be_translated.xls59 KBitamair

Comments

itamair’s picture

itamair commented

So no help from any ???
Was this so irrelevant?

johnv’s picture

johnv
Primary language Dutch
commented

Feeds only processes fields with language [und] (= undefined = LANGUAGE_NONE).
You might accomplish this by finding, applying and testing patches. You can find them searching on keyword 'language' .

tricasse’s picture

tricasse commented

Or see http://drupal.org/project/feeds_et.

richar’s picture

richar commented
StatusFileSize
new vucabulary_to_be_translated_0-1.xls18 KB

This its the solution. Try.

megachriz’s picture

megachriz
Primary language Dutch
commented
Component: Feeds Import » Code
Category: Bug report » Feature request
Issue summary: View changes
Status: Active » Closed (duplicate)

Since Feeds 7.x-2.0-beta2 there is integration with the Entity Translation module, so now you can specify a language for each mapping target that supports multilinguality. This was fixed in #1183440: Multilingual Feeds - Make field import language-aware.