The attached patch was mostly started to clean up the translatable strings and bring they in sync with CCK and core. While I was on the code I saw many other minor issues and fixed them together.

CommentFileSizeAuthor
term_fields_translatable_strings_formAPI_review-D6.patch29.36 KBhass

Comments

b-prod’s picture

b-prod commented
Status: Reviewed & tested by the community » Fixed

Thanks for the formatting!

tkotisis’s picture

tkotisis commented

This bug is resolved as fixed, but the patch does not seem to have found its way to the latest development snapshot (2009-Dec-03).
Since i need the translatable strings, what version can i apply this patch on?

On second notice, the patch has been applied, but i'm still unable to translate strings, e.g. "Term Fields" group string in the taxonomy terms.

b-prod’s picture

b-prod commented

The patch has been applied to the 6.x-1.x-dev release. If there are some issue about that, could you give me more details ?

hass’s picture

hass commented

If you'd like to translate your custom field names you need to install i18n package and make the strings translatable with i18n_strings module. Never done it, but this is the way how such fields will be translated.

Status: Fixed » Closed (fixed)

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