Hello,
I've developed a d6 site and trying to complete its internationalization
http://www.archiref.com/
It's a site where the content : images of architecture, projects, are mainly sync between both language (french and english).
Only pure text field could be relevant to node translation and I have got very little on each content type (1 or 2 / 20-20 fields)
The other fields are taxonomy in closed vocabulary (that I set as localizable)
and open taxonomy. that I don't want to translate (the automatic translation of taxonomy tags between languages seems more a problem than a solution) per aps I change my mind though
I have also numeric fields, that are purely non translatable for exemple surface of the lot = 2000 m2
I allow people to define this value in the unit of their choice between US system and EU system. sq inch or m2. thanks to the unit module.
And the I have node reference fields, that seem to me the more complex problem involved by node translation.
For exemple I have a project node that need to be related to a designer node. If I make everything translatable, It would be 4 node for each project/designer association, and I will always have to make special things to relate the project to their designer.
So I plan to migrate this site in D7 next year, and I would like to know what is the best strategy to map d6 fields in order d7 one could be translatable in the field translation system that seem the global drupal direction ?
Do you think I should set my content type in d6 to be translatable. Or should I wait to be in d7 ?
If I don't make them translatable I will lose the information that the node has been written in english of french. If I make it even if I don't enable "with translation", it will create two different versions of the same designer. And how could I make them unique again once in d7.
So as you see, I don't know exactly which path to take. Any advices ?