Discussion
· Oct 25

Language preference in Management Portal

The IRIS Management Portal is localized (translated) for some (many?) languages and the language used by the Management Portal interface is determined by the browser settings, often derived from the OS settings (can be changed).

This means that if a user, like me, want to use ONLY the English version of the Management Portal, each and every time you login you need to change the language. VERY annoying.

I know I can change the language configured in Browser, BUT, I want to use English for the IRIS management portal non for all my internet activity!

I feel uncomfortable using the localized version of the portal, the translation is often confusing.

Do not forget that while the portal is localized, ALL the documentation is available only in English, making it difficult for users, particularly new users, to match the documentation with the portal translation.

IMO, the ideal solution would be to add on option in the user definition where the Management Portal language can be forced, with default to "Browser language"

I have the feeling that it's hard for InterSystems developers to understand this issue we, international/foreign users, are facing simply because....they don't have this issue, so I feel they consider this unimportant.

I wanted to add this in our ideas portal but, not surprisingly, I found an existing entry similar to my idea, that I encourage to vote:

Remember Preferred language selection for Management Portal "forever"

For other non English (browser language 😊) users, what's your opinion? Do you often or always switch the Management Portal language to English?

Discussion (9)7
Log in or sign up to continue

the SMP portal "about" page, has an option to choose the language. However, this persists for the current session only (in %session object). I would try to go with the solution proposed by @Raj Singh 
to use a browser add-on that can modify HTTP headers: (e.g. the:  HTTP_ ACCEPT_LANGUAGE CGI variable).

Intersystems could think of adding a user defined language, but not on the user profile since non local users (e.g. LDAP) are non persistent, so a global like ^ISC.someName(user)=Language could be the "best" way.
We don't want to (or can't) modify classes for the portal (some of them doesn't have sources).
This is a good candidate for the "intersystems ideas"