Hi,

First thanks for this module, I play with i18n since 5.x and everything that has been done is awesome. And I'm happy to see some i18n stuff in core now ;)

With the new 6.x release of i18n, I noticed a strange behavior related to content type translation. I installed the drupal 6 with french package, so it translate the Story and Page default content type in french.

So I want to use the i18n content type module to provide an english translation for these content types.

To do that, I use the locale search form, no problem, it easily find the name content type string I want to translate, but there is a little bug

In the Screenshot 1, you can see in the listing that the fr is striked whereas this is the english translation that is missing. If I go to edit, drupal ask for an english translation as you can see in Screenshot 2 (Anglais mean English in french)

If I translate the string, this is for the english version so I think the error is in the listing (first screenshot) that show a striked fr instead of a striked en.

Another strange things is that if I go to create content, the translation are applied correctly. If I change the language prefix in the url, it show Article for french and Story for english, so it's ok.

But in the administration page of content types, the translation are not applied. If I go to /fr/admin/content/types or /en/admin/content/types, this is the french translation that I see.

So this is 2 minors problems, but 2 problems at all ;)

Do you have feedback to confirm or reverse this behavior ?

Regards,

zmove

CommentFileSizeAuthor
Screenshot 2.png3.38 KBzmove
Screenshot 1.png12.03 KBzmove

Comments

tomsolo’s picture

Status: Active » Closed (duplicate)

Duplicate bug reports -> http://drupal.org/node/228610

Bug in i18nstrings module, still active.

Small workaround:

1. Set default language -> english.
2. Go Translate interface -> search ex Article content type (in english)
3. Voila! U can now translate Article to french.

cheers