hi Jose and eventually others code maintainers,
i'm actually running CVSs versions of 4.7.0 and i18n.module and translation.module i am implementing taxonomies in order to categorize and organize contents. The problem is relate to term translation and consequent page categorization.
If I have a fruit and vegetables taxonomy and i wrote the italian version of "Cabbages" page, i'd like to categorize that page under (verde, verdura) that are italian category names for "green" (cabbages' colour) and "vegetables" (cabbages' familiy) ... actually is only possible to do this if pages ARE under the same language despite the translation ...
if i want to have the same content organized in both english and italian ... actually I have to define corrispondencies within the same vocabulary ... so all Fruits (al fruits names) and Frutti (all corresponding italian names) SHALL be in the same vocabulary in order to establish corrispondencies between terms ... i think is not correct.
IMHO there should be a mistake ... when you create a content - for example drupal presents you the categories (eg. vocabularies) DEFINED for that language ... so if I use
- one vocabulary (binded to one language only!!!) i can categorize the content only within that one language
- two vocabulary each one in one language, the system let me choose the correct taxo-term in the correct language
if i run http://www.myfruits.org/?q=it/admin/taxonomy/4/translation and all the term translations are done within an "en" vocabulary it will not categorize the content as "italian" content ...
In the above fuirts&veg. example, IMHO is necessary to define one vocabulary named fruits with all the fuits name in english and a second vocabulary named frutti in italian containig all the fruits name in italian ...
NOW what IMHO is necessary to do to the translation.module ... ?
It is necessary to fix the TRANSLATION interface logic for terms translation (what now is under
http://www.myfruits.org/?q=it/admin/taxonomy/4/translation) in order to
- define, for each vocabulary, which one is the correct vocabulary to be considerd for translation from a language to another - please note that actually vocabularies are ALREADY language-typed (the have a "language" field yet) ... say Fruits--Frutti and Colours--Colori Names--Nomi and so on ...
- fix the translation page in order to present selected vocabularies instead of the single one ... eg. When i have to create association between two vocabularies i have to associates voices from a vocabulary.language="en" taxo to a vocabulary.language="it" taxo
hope to clear enogh.
Comments
Comment #1
sunThis module was a module in Drupal core since Drupal 6. It is going to be replaced with an alternative implementation developed by the i18n team.