Posted by ingo86 on September 23, 2008 at 5:33pm
Hi all,
I wanna crosspost here my issue because there's something that i can't understand into drupal translation mechanism or something that could be better.
Here's the topic:
http://drupal.org/node/312216
As said in the first comment I see that someone's having the same issue with D5.
Thanks,
ingo86
Comments
Ok guys, I looked better to i18n and
Ok guys, I looked better to i18n and i see some things that I don't understand. I wanna talk about implementation of i18n because it is a bit unfriendly.
In drupal every content is a node. With i18n every node has a language. I think that this is good and we can move forward. Node 23 for example is in italian language and no other. The translation of this node in english is node 24 and we are again ok. A simple sql table with foreign key could match node 23 and 24 to be the same conceptual node (at high level) but different node at lower level.
Now there are some things that are not nodes, like user interface, we can use "Translate Interface" to translate it. Here a last-minute question(i haven't thinked too much about it): why two nodes and not always the same translate mechanism for all?
Here I have a usability advice too: It is difficult to understand why sometimes the language is striked. I think that a line that explain it is required.
For me the problems comes when you have to translate a content, as said in my issue. Specifically I wanna focus upon the theme that has to be shown after clicking on "Translate" tab.
After thinking about it i see that there are lot of scenarious, you can use only one theme, two themes or more than two and the best solution for this is to ask this parameter to the user. Let me know if you guys agree with this.
Another thing that i wanna focus is the node association with the language. Trying to reach an italian node from the user interface set to english I get the page without primary links. anyone knows why?
There are another thing that I see and dislike into this module: too much config pages, "Language", "Multilingual site", "Translate interface", why don't make them one? Or at most two.
Finally, I wanna thank all the guys that makes this module, it's really the best localization module that i ever seen into a cms.
Ingo86