Jehan

Chouby: as Mokona84 says, yes first of all, proper names will normally always be the same.
In my last blog post, for instance, I was speaking about some software programs. So I tagged the post with their names. And they are the same, whatever languages.

And now even common names, there are a lot of cases where they are the same across languages. For instance because they are recent and come from English. As the perfect example, in French, we would translate “tag”… by using the English word “tag”.

So yeah a solution could be as you propose: automatically creating translation tags and categories (and if in some cases, they are the same, well we can modify them).

But I think a better solution is that a tag is language-free by default. Then if the user wishes to specialize it to a lang and make some translation, one can do it afterwards.
Why I think it is better design: first it avoids useless duplication of tags; second in case of translated tags, we don’t need to go in the tag edition page immediately (we can just create the new tag in the normal post edition page, and later associate it to its translation if desired). In other word, a much cleaner and easier-to-use design.

Hi,

I see. Just tested, it works. Thanks.

I still think that’s far from ideal. Categories don’t evolve very fast, but tags have the tendency to evolve much more.

If we have like 3 or 4 languages, for each tag, we have to duplicate them in a counter-intuitive way in WordPress tag editor (because as we cannot use the same slug as the original tag, we cannot create the duplicate tags from the post edition page), that’s pretty laborious.

I would really suggest to make both tags and categories as being generic across all langs, still giving possibility to create a translation afterwards, but not forcing it from the start.
Thanks anyway for the answer.