localization

[kevin...@gmail.com]

Hi,

I'm having trouble getting localization to work with owf.  I can only make it work in CAS authentication.

1.  Setting the "messageSource" bean(ReloadableResourceBundleMessageSource) can only be done from my securitycontext.xml file.  If I try it from applicationContext.xml, it doesn't work

2.  I can't set the defaultLocale.  I tried the following in my dispatcher-servlet.xml:

<bean id="localeResolver" class="org.springframework.web.servlet.i18n.CookieLocaleResolver">

<property name="defaultLocale" value="fr" />

</bean>

But I can see it work if i modify cas-servlet.xml

3.  I can't get the localeChangeInterceptor to work.  I tried the following in my dispatcher-servlet.xml:

<bean id="localeChangeInterceptor"

    class="org.springframework.web.servlet.i18n.LocaleChangeInterceptor">

    <property name="paramName" value="lang" />

</bean>

Am I not building it properly or missing some configuration?

[Tina Coleman]

Localization support was dropped from OWF many releases ago, based on a perceived lack of use, and even then was provided through an application toggle within OWF itself, rather than from watching the browser environment.  The support you see in CAS is from the jasig underlying CAS application, and is not something the OWF platform itself provides or tests. 

 

 

Tina Coleman

NEXTCENTURYCORPORATION
7075 Samuel Morse Drive, Suite 250 | Columbia, MD 21046
m 443.545.3100 | f 443.285.0799 |www.nextcentury.com

--
You received this message because you are subscribed to the Google Groups "ozoneplatform-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ozoneplatform-u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kevin Wong]

Thanks very much for this.  I didn't know it was dropped since I thought it was apart of the underlying spring framework

--
You received this message because you are subscribed to a topic in the Google Groups "ozoneplatform-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ozoneplatform-users/JuBHcev58fA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ozoneplatform-u...@googlegroups.com.

[kevin...@gmail.com]

In that case, would it be possible to push a "locale" parameter through the login form and have it accessible afterwards?

To unsubscribe from this group and stop receiving emails from it, send an email to ozoneplatform-users+unsub...@googlegroups.com.

[Tina Coleman]

The better technology approach is to handle it via the same Spring filter, and pull it through, rather than relying on a login form that may or may not be applied in all system deployments.  The challenge in including it isn’t in making the setting available, it’s in appropriately handling it within the application, and then further providing it to widgets. 

 

It was originally dropped more so for the cost to verify/validate that all strings were (1) only being pulled from resource files, and that (2) all language file variants remained in synch.  Definitely a doable thing, but does consume time and energy to both set it up, and then make sure it stays correct. 

To unsubscribe from this group and stop receiving emails from it, send an email to ozoneplatform-u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "ozoneplatform-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ozoneplatform-u...@googlegroups.com.

[Kevin Wong]

Thanks again for the reply.  Does this mean I can't do this with what is provided in the the OWF bundle?

[Mario Savard]

Hello,

        Can someone confirm this question (see above) ? We are trying to see if we could translate OWF but it seems it is not possible using the OOTB OWF. We are using OWF 7.17

Mario

To unsubscribe from this group and stop receiving emails from it, send an email to ozoneplatform-users+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "ozoneplatform-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ozoneplatform-users/JuBHcev58fA/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ozoneplatform-users+unsub...@googlegroups.com.

[Ross Pokorny]

That is correct, OWF still does not have localization support. The only way
to change the language of the application would be to fork the code and modify
all strings of text that appear in the UI.

Ross Pokorny

On Monday, September 26, 2016 2:02:10 PM EDT Mario Savard wrote:
> Hello,
> Can someone confirm this question (see above) ? We are trying to
> see if we could translate OWF but it seems it is not possible using the
> OOTB OWF. We are using OWF 7.17
>
> Mario
>
> On Friday, May 2, 2014 at 4:46:29 PM UTC-4, Kevin Wong wrote:
> > Thanks again for the reply. Does this mean I can't do this with what is
> > provided in the the OWF bundle?
> >
> >
> > On Thu, May 1, 2014 at 3:18 PM, Kevin Wong <kevin...@gmail.com
> >
> > <javascript:>> wrote:
> >> Thanks very much for this. I didn't know it was dropped since I thought
> >> it was apart of the underlying spring framework
> >>
> >>
> >> On Thu, May 1, 2014 at 3:17 PM, Tina Coleman <tina.c...@nextcentury.com
> >>
> >> <javascript:>> wrote:
> >>> Localization support was dropped from OWF many releases ago, based on a
> >>> perceived lack of use, and even then was provided through an application
> >>> toggle within OWF itself, rather than from watching the browser
> >>> environment. The support you see in CAS is from the jasig underlying
> >>> CAS
> >>> application, and is not something the OWF platform itself provides or
> >>> tests.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Tina Coleman
> >>>

> >>> *NEXT**CENTURY*CORPORATION

> >>> 7075 Samuel Morse Drive, Suite 250 | Columbia, MD 21046
> >>> m 443.545.3100 | f 443.285.0799 |www.nextcentury.com
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>

> >>> *From:* ozoneplat...@googlegroups.com <javascript:> [mailto:
> >>> ozoneplat...@googlegroups.com <javascript:>] *On Behalf Of *
> >>> kevin...@gmail.com <javascript:>
> >>> *Sent:* Thursday, May 01, 2014 3:08 PM
> >>> *To:* ozoneplat...@googlegroups.com <javascript:>
> >>> *Subject:* localization

> >>>
> >>>
> >>>
> >>> Hi,
> >>>
> >>>
> >>>
> >>> I'm having trouble getting localization to work with owf. I can only
> >>> make it work in CAS authentication.
> >>>
> >>>
> >>>
> >>> 1. Setting the "messageSource"
> >>> bean(ReloadableResourceBundleMessageSource) can only be done from my
> >>> securitycontext.xml file. If I try it from applicationContext.xml, it
> >>> doesn't work
> >>>
> >>> 2. I can't set the defaultLocale. I tried the following in my
> >>> dispatcher-servlet.xml:
> >>>
> >>> <bean id="localeResolver"
> >>> class="org.springframework.web.servlet.i18n.CookieLocaleResolver">
> >>>
> >>> <property name="defaultLocale" value="fr" />
> >>>
> >>> </bean>
> >>>
> >>> But I can see it work if i modify cas-servlet.xml
> >>>
> >>>
> >>>
> >>> 3. I can't get the localeChangeInterceptor to work. I tried the
> >>> following in my dispatcher-servlet.xml:
> >>>
> >>> <bean id="localeChangeInterceptor"
> >>>
> >>>
> >>> class="org.springframework.web.servlet.i18n.LocaleChangeInterceptor">
> >>>
> >>> <property name="paramName" value="lang" />
> >>>
> >>> </bean>
> >>>
> >>>
> >>>
> >>> Am I not building it properly or missing some configuration?
> >>>
> >>>