I have installed the i18n modulules, and enabled several of them - ie., multilingual blocks, multilingual menus and multilingual profiles.

1) I add a custom field to my users' profiles - defining custom name for the field, custom description, etc.
2) I go into Site building -> Translate interface -> Refresh, and I refresh all strings (and just for good measure, also update all translations)
3) When I visit a user's profile page in a non-default language, I would expect the l10n client module to pick up the new strings for the new fields and their descriptions - but it doesn't. Those strings are never listed.
4) If I go to Site building -> Translate interface -> Search, I can find the untranslated strings, and translate them there.
5) I can visit a profile page in a non-default language, and see that my translated strings actually appear, and are being used - however, they NEVER appear in the l10n client's list.

The same seems to apply to other modules - ie., if I change the name of menu items, or blocks - that is, I can translate the new strings by going searching them manually through Drupal's standard 'translate interface', but l10n client seems totally unaware that the strings even exist.

Comments

gábor hojtsy’s picture

Category: bug » feature
Status: Active » Closed (duplicate)

This is a missing feature, not a bug. i18n module uses the textgroups feature of Drupal 6 to store translations in different groups, and l10n_client only uses the default textgroup (the built-in interface group as seen on the UI). http://drupal.org/node/287210 points to adding more features, including support for i18ns other textgroups (it is not trivial, since they use a different method to translate stuff then the built in textgroup).

icouto’s picture

@Gábor, thank you for the clarification. I'll keep hoping for an overhaul in D7! :-)

aufumy’s picture

issue for localization client
http://drupal.org/node/361147