The current implementation of the Seperated taxonomy term formatter does not support localization for term names. My suggestion would be to create an extra formatted "Seperated (localized)" so it will match the Link and Plain text formatter variations given by the i18n module.

I already have this code running in a custom module. If there is any interest i would be glad to create a patch for this.

CommentFileSizeAuthor
#5 1902046-5.patch2.87 KBswentel
#4 1902046-4.patch1.91 KBswentel
#2 localized_version_of_seperated_formatter.patch2.31 KBericmulder1980

Comments

swentel’s picture

swentel commented

Sounds interesting - would a simple if (module_exists('i18n_taxonomy')) { } do the trick, or would it be handier just to have a separate formatter ? IIRC, i18n creates separate formatters anyway right ? I'd commit the patch if there's one :)

ericmulder1980’s picture

ericmulder1980 commented
Status: Needs review » Active
StatusFileSize
new localized_version_of_seperated_formatter.patch2.31 KB

Here you go. In formatter info i have added an extra formatter with a check for 18n_taxonomy

module_exists('i18n_taxonomy')

In the formatter_view i have used exactly the same code as the seperated formatter but i replaced the $term->name with a localized version fetched by 18n.

i18n_taxonomy_term_name($term, $language->language);
ericmulder1980’s picture

ericmulder1980 commented
Status: Active » Needs review
swentel’s picture

swentel commented
Status: Active » Needs review
StatusFileSize
new 1902046-4.patch1.91 KB

I've simplified the patch a little, could you quickly check if this still works ?

swentel’s picture

swentel commented
Status: Needs review » Fixed
StatusFileSize
new 1902046-5.patch2.87 KB

This is what ultimately was committed.

Status: Fixed » Closed (fixed)

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