I'm opening this issue as a support request and in the RealName project's issue queue because I don't know if this is a bug or a feature request and whether it belongs to Drupal core, i18n (i18n_block in particular), entity_translation or whatever???...

I don't know if the core "Who's new" block is language-aware when it comes to the content it displays. I managed to translate the real name field of users and now the block displays real names instead of account names, but it always displays them in the site's default language no matter what language the site is switched to. So when the site's language is English, the block's title is English too and the user real names are listed in their English version as well. If I switch the site to Italian, the block's title is in Italian (as expected), but the users' names are listed in English. If I set the site's default language to Italian, it happens the other way around: the block's title follows the site's language, but the user's real names are always in Italian.

So, what am I doing wrong? Is this a bug? Should I file it as a feature request instead? Can it be solved in this project here, or should it be switched to core/i18n/whatever???

Comments

klonos’s picture

Title: RealName and the core "Who's new" block in a multilingual site. » The Drupal core "Who's new" block in a multilingual site always displays the users' real names in the site's default language.
Project: Real Name » Internationalization
Component: Translations » Blocks
Category: support » bug

I'm changing this to a bug and switching to the i18n project. If I don't get any useful reply there, I'll have to assume this is a Drupal core bug and switch to it.

PS: I think this is similar: #1331724: All translations of forum topics are displayed - no matter what language the site is switched to.

jose reyero’s picture

Status: Active » Closed (won't fix)

This module doesn't do anything with field values so please post somewhere else (which I don't think is core either).

klonos’s picture

Project: Internationalization » Real Name
Component: Blocks » Code
Status: Closed (won't fix) » Active

...back to RealName then and changing status to "active" since it's an existing issue that hasn't been addressed.

dave reid’s picture

Status: Active » Postponed (maintainer needs more info)

Here's the deal - the core format_username() function lacks any kind of language context. I'm not sure how we can work around this in Real name either.

klonos’s picture

dave reid’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

This is unfortunately not something we can fix core's behavior. You might be interested in following #1775818: Multilingual support though.