Hi,

I am trying this module on drupal 6.1. I have two sites, both multilanguage (Spanish, and English), one of them has Spanish as the default language, lets call it ES. When I translate a string from the Content type text group on ES, the translated string is stored as a translation to English (but it is supposed to be an Spanish string). I haven't seen the 'locales_target' table and the translated entry has a language value 'en'.

I don't know if this is a bug on the Internationalization module, it may be a bug of the Content Translation module. Also, I don't know if this bug also affect the other text groups added by the Internationalization module: Blocks, Taxonomy, etc.

Comments

jose reyero’s picture

jose reyero commented
Assigned: Unassigned » jose reyero
Priority: Normal » Critical

Yeah, you can call it a bug in i18nstrings module.

It may not be working well when default language is other than English working on that.

jose reyero’s picture

jose reyero commented
Priority: Critical » Normal

I've been trying and in spite of some interface glitches, it seems you can create English translation if the language default is different.

So if this is the case -please confirm- this just needs some UI polishing, just lowering the issue priority but still open.

jose reyero’s picture

jose reyero commented
Status: Active » Postponed (maintainer needs more info)
jose reyero’s picture

jose reyero commented
Status: Postponed (maintainer needs more info) » Fixed
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.