Hello Georgen, 

as far as I know, unfortunately no. 

Here are some possible workarounds. 
Maybe you know them already or you could test it. 

########

1. Temporarily change the Regional format to English (United States) or English (United Kingdom) → Go to Control Panel → Region → Formats tab → Set "Format" to English (United States) → The PAfE ribbon will then display in English. → Disadvantage: This also changes decimal/thousands separators, date formats, etc., across all applications - often not desired in Switzerland (where you typically want to keep comma as decimal separator).
2. Use a hybrid locale like "English (South Africa)" → Some users report that setting the format to "English (South Africa)" provides an English UI while still using European-style number and date formats (comma as decimal, period as thousands separator). → Worth testing - success varies depending on Windows version and PAfE version.
3. Manual override by replacing files in the LanguageResources folder (most commonly recommended workaround)
   • Path: %USERPROFILE%\AppData\Roaming\Cognos\Office Connection\LanguageResources (or sometimes under Local instead of Roaming, depending on setup)
   • This folder contains the .resources files for each language (e.g., files with "de" for German).
   • Solution: Copy the English ("en") .resources files and rename them to replace the German ("de") ones (overwrite the de.* files with renamed copies of en.*). → PAfE will then load the English resources when it expects "de".
   • Advantage: Keeps your Swiss regional format settings intact while forcing the PAfE ribbon UI to English.
   • Disadvantage: Needs to be done per user; may need to be repeated after updates or reinstalls; not centrally manageable without deployment scripting.
4. No real override available in configuration files IBM documentation (e.g., articles about "Run Cognos Office components in English in localized Microsoft Windows environment") confirms that the file replacement method (option 3) is the supported/officially mentioned approach. There is no registry key, TM1Features.json setting, CognosOfficeReportingSettings.xml entry, or similar that directly allows overriding the language independently of the system locale.

The cleanest non-disruptive solution for most users is option 3 (the LanguageResources file rename trick), as it preserves regional number/date formatting while only changing the PAfE UI language.

#####

Maybe you get some different feedback.
With best regards, 
Vitalij

Thanks Vitalij, I got the same when searching but looking to avoid hacks and changing file names which need to be updated with each new version of PAfE.

Hello Georgen, 

as far as I know, unfortunately no. 

Here are some possible workarounds. 
Maybe you know them already or you could test it. 

########

1. Temporarily change the Regional format to English (United States) or English (United Kingdom) → Go to Control Panel → Region → Formats tab → Set "Format" to English (United States) → The PAfE ribbon will then display in English. → Disadvantage: This also changes decimal/thousands separators, date formats, etc., across all applications - often not desired in Switzerland (where you typically want to keep comma as decimal separator).
2. Use a hybrid locale like "English (South Africa)" → Some users report that setting the format to "English (South Africa)" provides an English UI while still using European-style number and date formats (comma as decimal, period as thousands separator). → Worth testing - success varies depending on Windows version and PAfE version.
3. Manual override by replacing files in the LanguageResources folder (most commonly recommended workaround)
   • Path: %USERPROFILE%\AppData\Roaming\Cognos\Office Connection\LanguageResources (or sometimes under Local instead of Roaming, depending on setup)
   • This folder contains the .resources files for each language (e.g., files with "de" for German).
   • Solution: Copy the English ("en") .resources files and rename them to replace the German ("de") ones (overwrite the de.* files with renamed copies of en.*). → PAfE will then load the English resources when it expects "de".
   • Advantage: Keeps your Swiss regional format settings intact while forcing the PAfE ribbon UI to English.
   • Disadvantage: Needs to be done per user; may need to be repeated after updates or reinstalls; not centrally manageable without deployment scripting.
4. No real override available in configuration files IBM documentation (e.g., articles about "Run Cognos Office components in English in localized Microsoft Windows environment") confirms that the file replacement method (option 3) is the supported/officially mentioned approach. There is no registry key, TM1Features.json setting, CognosOfficeReportingSettings.xml entry, or similar that directly allows overriding the language independently of the system locale.

The cleanest non-disruptive solution for most users is option 3 (the LanguageResources file rename trick), as it preserves regional number/date formatting while only changing the PAfE UI language.

#####

Maybe you get some different feedback.
With best regards, 
Vitalij

I understand. 
Let's wait for further feedback. 

Thanks Vitalij, I got the same when searching but looking to avoid hacks and changing file names which need to be updated with each new version of PAfE.

Hello Georgen, 

as far as I know, unfortunately no. 

Here are some possible workarounds. 
Maybe you know them already or you could test it. 

########

1. Temporarily change the Regional format to English (United States) or English (United Kingdom) → Go to Control Panel → Region → Formats tab → Set "Format" to English (United States) → The PAfE ribbon will then display in English. → Disadvantage: This also changes decimal/thousands separators, date formats, etc., across all applications - often not desired in Switzerland (where you typically want to keep comma as decimal separator).
2. Use a hybrid locale like "English (South Africa)" → Some users report that setting the format to "English (South Africa)" provides an English UI while still using European-style number and date formats (comma as decimal, period as thousands separator). → Worth testing - success varies depending on Windows version and PAfE version.
3. Manual override by replacing files in the LanguageResources folder (most commonly recommended workaround)
   • Path: %USERPROFILE%\AppData\Roaming\Cognos\Office Connection\LanguageResources (or sometimes under Local instead of Roaming, depending on setup)
   • This folder contains the .resources files for each language (e.g., files with "de" for German).
   • Solution: Copy the English ("en") .resources files and rename them to replace the German ("de") ones (overwrite the de.* files with renamed copies of en.*). → PAfE will then load the English resources when it expects "de".
   • Advantage: Keeps your Swiss regional format settings intact while forcing the PAfE ribbon UI to English.
   • Disadvantage: Needs to be done per user; may need to be repeated after updates or reinstalls; not centrally manageable without deployment scripting.
4. No real override available in configuration files IBM documentation (e.g., articles about "Run Cognos Office components in English in localized Microsoft Windows environment") confirms that the file replacement method (option 3) is the supported/officially mentioned approach. There is no registry key, TM1Features.json setting, CognosOfficeReportingSettings.xml entry, or similar that directly allows overriding the language independently of the system locale.

The cleanest non-disruptive solution for most users is option 3 (the LanguageResources file rename trick), as it preserves regional number/date formatting while only changing the PAfE UI language.

#####

Maybe you get some different feedback.
With best regards, 
Vitalij

This allows me to advertise the PAfE blog. 😄

Yes, you can control the language PAfE uses by setting the PAfELocale centrally managed option, which overrides the OS Regional format. Check out the video in the PAfE blog post.

The post "PAfE-PASS Centrally Managed Options" covers how administrators can centrally manage PAfE settings - including PAfELocale - and deploy them consistently across all users. The embedded video walks through the configuration.

https://community.ibm.com/community/user/blogs/xavier-osorio/2026/04/16/excel-meets-enterprise-planning-exploring-planning

The video when originally posted had some issues, but I believe it is now fully working. 

Good Luck, and let us know how it goes. 

X