Make "WordPress is also available in..." string translatable

[SergeyBiryukov]

Currently the links to local sites displayed on WordPress.org for international visitors are partly English, partly translated:

WordPress is also available in Русский.
WordPress support forums are also available in Русский.

For better user experience, we should allow l10n teams to translate these strings in Rosetta. Due to different grammatical cases, the language name would probably need a separate context for these links.

[vanillalounge]

I would even go so far as to suggest that if, at the end of the language detection progress, the case we arrive at is US English, then show nothing at all. In other words:

• If language is detected:
• * If the string is translated, show that
• * If the string is not translated, show "WordPress is also available in <language-name-in-English>
• Language is not detected, show nothing.

[nacin]

Replying to vanillalounge:

I would even go so far as to suggest that if, at the end of the language detection progress, the case we arrive at is US English, then show nothing at all.

That's what already happens; we don't show "WordPress is also available in English." :-)

I guess what I see you are proposing is that if the string isn't translated, we show "WordPress is also available in Russian", not "WordPress is also available in Русский"? I'm not sure I see the benefit.

[vanillalounge]

I'm not sure I see the benefit.

There's no "benefit" (or disadvantage, for that matter), it's just proper grammar. "WordPress is also available in Русский" is neither correct English, nor is it correct Russian.

[thee17]

But there is a case of multiple languages. i.e. in Canada it displays "WordPress is also available in English and Français."

[samuelsidler]

Migrated to ​#meta106.