Anonymous_User Absent Member.
Absent Member.
266 views

HPD language selection


I have noticed that HPD determines localization based on the
Accept-Language header from the browser. There seems no other way to
influence this behaviour (i.e. user input). Did I overlook some settings
or is this a product limitation?

The reason I ask: all browsers are installed with default en-us at our
university (because of international students), but the majority of
users are dutch. We would like the user to decide in what language HPD
is being displayed, or through a HTTP param which NAM could serve to the
public resource HPD (i.e. 〈=nl).


--
sveldhuisen
------------------------------------------------------------------------
sveldhuisen's Profile: https://forums.netiq.com/member.php?userid=1813
View this thread: https://forums.netiq.com/showthread.php?t=50333

Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: HPD language selection

On 03/21/2014 09:54 AM, sveldhuisen wrote:
>
> I have noticed that HPD determines localization based on the
> Accept-Language header from the browser. There seems no other way to
> influence this behaviour (i.e. user input). Did I overlook some settings
> or is this a product limitation?
>
> The reason I ask: all browsers are installed with default en-us at our
> university (because of international students), but the majority of
> users are dutch. We would like the user to decide in what language HPD
> is being displayed, or through a HTTP param which NAM could serve to the
> public resource HPD (i.e. 〈=nl).
>
>

Greetings,
If you change the language setting in the browser, do a clear of the
cache in the browser, then the page will render in the language (as long
as language is one we support).



--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HPD language selection

On 03/21/2014 10:13 AM, Steven Williams wrote:
> On 03/21/2014 09:54 AM, sveldhuisen wrote:
>>
>> I have noticed that HPD determines localization based on the
>> Accept-Language header from the browser. There seems no other way to
>> influence this behaviour (i.e. user input). Did I overlook some settings
>> or is this a product limitation?
>>
>> The reason I ask: all browsers are installed with default en-us at our
>> university (because of international students), but the majority of
>> users are dutch. We would like the user to decide in what language HPD
>> is being displayed, or through a HTTP param which NAM could serve to the
>> public resource HPD (i.e. 〈=nl).
>>
>>

> Greetings,
> If you change the language setting in the browser, do a clear of the
> cache in the browser, then the page will render in the language (as long
> as language is one we support).
>
>
>

Greetings,
Or, you can have them set their preferred Language in the User
Application (it maps the attribute srvprvPreferredLocale). Once you
have logged you will see things for that language

Browser => English
srvprvPreferredLocale => Spanish

You will see text in Spanish



--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HPD language selection

On 03/21/2014 11:13 AM, Steven Williams wrote:
> On 03/21/2014 10:13 AM, Steven Williams wrote:
>> On 03/21/2014 09:54 AM, sveldhuisen wrote:
>>>
>>> I have noticed that HPD determines localization based on the
>>> Accept-Language header from the browser. There seems no other way to
>>> influence this behaviour (i.e. user input). Did I overlook some settings
>>> or is this a product limitation?
>>>
>>> The reason I ask: all browsers are installed with default en-us at our
>>> university (because of international students), but the majority of
>>> users are dutch. We would like the user to decide in what language HPD
>>> is being displayed, or through a HTTP param which NAM could serve to the
>>> public resource HPD (i.e. 〈=nl).
>>>
>>>

>> Greetings,
>> If you change the language setting in the browser, do a clear of the
>> cache in the browser, then the page will render in the language (as long
>> as language is one we support).
>>
>>
>>

> Greetings,
> Or, you can have them set their preferred Language in the User
> Application (it maps the attribute srvprvPreferredLocale). Once you
> have logged you will see things for that language
>
> Browser => English
> srvprvPreferredLocale => Spanish
>
> You will see text in Spanish
>
>
>

Greetings,
Just to finish up. Our applications use the following "if" kind of
approach:

1) srvprvPreferredLocale
2) Browser Locale setting
3) Default Locale for the Application

If #1 is set and the language is one that we support, then use it.
If #1 is not set, or the language is one that we do not support then
drop to #2

If #2 is set and the language is one that we support, then use it
If #2 is set to a language that we do not support then drop to #3

If #3, utilize the default language that is set for the User Application.



--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HPD language selection


Just an add on question on the topic.

Will you in the future releases add more settings like the
srvprvPreferredLocale as an example to the HPD view.
As I see it the HPD will be exposed to all Users and eventually also
users who are proxy users/ team managers and so on while User
Application will be mostly used for administration.

Just curious on the general direction in the development.

Cheers


--
joakim_ganse
------------------------------------------------------------------------
joakim_ganse's Profile: https://forums.netiq.com/member.php?userid=159
View this thread: https://forums.netiq.com/showthread.php?t=50333

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HPD language selection


Thanks Stevens, this makes sense. (Sorry for my late reply)

Steven Williams;242406 Wrote:
> On 03/21/2014 11:13 AM, Steven Williams wrote:
> > On 03/21/2014 10:13 AM, Steven Williams wrote:
> >> On 03/21/2014 09:54 AM, sveldhuisen wrote:
> >>>
> >>> I have noticed that HPD determines localization based on the
> >>> Accept-Language header from the browser. There seems no other way

> to
> >>> influence this behaviour (i.e. user input). Did I overlook some

> settings
> >>> or is this a product limitation?
> >>>
> >>> The reason I ask: all browsers are installed with default en-us at

> our
> >>> university (because of international students), but the majority of
> >>> users are dutch. We would like the user to decide in what language

> HPD
> >>> is being displayed, or through a HTTP param which NAM could serve to

> the
> >>> public resource HPD (i.e. 〈=nl).
> >>>
> >>>
> >> Greetings,
> >> If you change the language setting in the browser, do a clear of

> the
> >> cache in the browser, then the page will render in the language (as

> long
> >> as language is one we support).
> >>
> >>
> >>

> > Greetings,
> > Or, you can have them set their preferred Language in the User
> > Application (it maps the attribute srvprvPreferredLocale). Once you
> > have logged you will see things for that language
> >
> > Browser => English
> > srvprvPreferredLocale => Spanish
> >
> > You will see text in Spanish
> >
> >
> >

> Greetings,
> Just to finish up. Our applications use the following "if" kind of
> approach:
>
> 1) srvprvPreferredLocale
> 2) Browser Locale setting
> 3) Default Locale for the Application
>
> If #1 is set and the language is one that we support, then use it.
> If #1 is not set, or the language is one that we do not support then
> drop to #2
>
> If #2 is set and the language is one that we support, then use it
> If #2 is set to a language that we do not support then drop to #3
>
> If #3, utilize the default language that is set for the User
> Application.
>
>
>
> --
>
> Sincerely,
> Steven Williams
> Lead Software Engineer
> NetIQ



--
sveldhuisen
------------------------------------------------------------------------
sveldhuisen's Profile: https://forums.netiq.com/member.php?userid=1813
View this thread: https://forums.netiq.com/showthread.php?t=50333

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.