A fix for this issue is now available for Confluence Server customers.
Upgrade now or check out the Release Notes to see what other issues are resolved.

+1

When testing Confluence as a potential tool to document my customers lifecycle management, I had installed the cloud version (English default) to verify all of the features and based our decision to use Confluence as our company's internal wiki and our customer'S documentation management system.
As a company based in Quebec, Canada, our internal users are French, but our client base is multi-lingual. Our current server installation of Confluence has a default language of French, but as a site admin, all of the blueprints that I use for new spaces for my English clients generate French texted spaces and pages. This will also be true for all of my English customers; any blueprints they use will have French text in their results.

I also strongly agree with Ricksoft. The workaround is not realistic. I could understand changing my user profile language to another language to create spaces or pages, but I dislike the idea of changing the default language of Confluence to my language (English), as it affects other users of Confluence.

Hi atlassian_support1, completely agree that this is not going to be feasible for everyone, this is more there for those who weren't aware of the global setting. We're looking into it further.

ensure that the global language (Confluence Admin > Languages) is set to the same language as the end user's

We think this workaround is not realistic.

I checked and the string has already been translated. I will double check why it's not coming through when I load the new translations in for 5.8.

I wonder how to deal with none-English languages for blueprint labels. As far as I'm aware, they are always in English (required for functionality of the index page).
Imagine Confluence is used in France, China or Japan where English is not understood by the majority of people.

On the other hand, what about mixed installations (some people use English, some German, some what-ever) in their personal settings. What should the blueprints come up with? Depending on the personal settings of the current user? The next user who accesses the same page (created from blueprint) may have different language setting and possibly not understand what's written in the page. This is a big potential issue for world-wide organizations. What should we do? What should we advise Atlassian to do?
The easiest way would be to uninstall all language plugins and allow English only. Though I see that this is not an option in some countries, namely in Far-East.

Same problem in Confluence instance 5.6.6.
Blue prints are displayed in English.

1. Set the language setting in User profile as Japanese.
2. Set language in Confluence Admin > Languages as English.
3. Create a Product Requirements.

It is preferable to reflect user profile language.