Localization: user selectable UICulture w/ UICulture = auto

I am running into a problem of mixing UICulture = auto and allowing users to
select culture using a dropdown list.

I am detecting a querystring, "setlang", and when found, setting the
CurrentUICulture to what's specified in the querystring. Since I want to
allow UICulture auto detecting, I add UICulture = "auto" to page directive on
each page.

Now, here is the problem: I don't know on what event (page or application) I
should set the CurrentUICulture based on the querystring, "setlang".

Since the UICulture = "auto", I cannot utilize any of the application events
to set CurrentUICulture. I could use PostAcquireRequestState if UICulture is
not auto on in page directive.

I cannot use page event effectively either. I tried to set CurrentUICulture
based on querystring in Page.PreInit. It seems that if I programmatically set
control's text to a resource string (textbox1.text =
resources.language.astring) everything works fine, but if I use explicit
binding declaratively on the control (<%$ Resources: language, astring%>), it
ignores the CurrentUICulture set in Page.PreInit and displays the string from
the culture the page auto detects. Not being able to bind declaratively is a
produtivity killer and therefore not acceptable.

Can anyone shed some light on how I can accomplish this?
I will repeat what I want to accomplish:

1) UICulture = "auto" on page directive (or can I set it somewhere else?)
2) user selectable cultures
3) being able to bind resources to control declaratively (<%$ Resources:
language, astring%>)

Advertisements

Guest

Cheers,
Tom Pester
> Hi,
>
> I am running into a problem of mixing UICulture = auto and allowing
> users to select culture using a dropdown list.
>
> I am detecting a querystring, "setlang", and when found, setting the
> CurrentUICulture to what's specified in the querystring. Since I want
> to allow UICulture auto detecting, I add UICulture = "auto" to page
> directive on each page.
>
> Now, here is the problem: I don't know on what event (page or
> application) I should set the CurrentUICulture based on the
> querystring, "setlang".
>
> Since the UICulture = "auto", I cannot utilize any of the application
> events to set CurrentUICulture. I could use PostAcquireRequestState if
> UICulture is not auto on in page directive.
>
> I cannot use page event effectively either. I tried to set
> CurrentUICulture based on querystring in Page.PreInit. It seems that
> if I programmatically set control's text to a resource string
> (textbox1.text = resources.language.astring) everything works fine,
> but if I use explicit binding declaratively on the control (<%$
> Resources: language, astring%>), it ignores the CurrentUICulture set
> in Page.PreInit and displays the string from the culture the page auto
> detects. Not being able to bind declaratively is a produtivity killer
> and therefore not acceptable.
>
> Can anyone shed some light on how I can accomplish this? I will repeat
> what I want to accomplish:
>
> 1) UICulture = "auto" on page directive (or can I set it somewhere
> else?)
> 2) user selectable cultures
> 3) being able to bind resources to control declaratively (<%$
> Resources:
> language, astring%>)

Advertisements

Thanks for your reply. Actually what's in the blog is what I did in my code
already. The only difference is that he uses PreRequestHandlerExecute and I
used PostAcquireRequestState (no difference)

However, I found the solution: if you want uiculture=auto while still
allowing user to change uiculture, the only way is to set uiculture = auto in
web.config and not on the page. When uiculture = auto is set in web.config,
we can use application event to override it, but when uiculture=auto is set
in page directive, you cannot override it for declaratively bound resources.

"" wrote:
> Hi Samuel,
>
> I think the last section of this blog post can help you :
> http://dotnetjunkies.com/WebLog/anoras/archive/2005/02/13/54271.aspx
>
> Let me know if you have any more questions..
>
> Cheers,
> Tom Pester
>
> > Hi,
> >
> > I am running into a problem of mixing UICulture = auto and allowing
> > users to select culture using a dropdown list.
> >
> > I am detecting a querystring, "setlang", and when found, setting the
> > CurrentUICulture to what's specified in the querystring. Since I want
> > to allow UICulture auto detecting, I add UICulture = "auto" to page
> > directive on each page.
> >
> > Now, here is the problem: I don't know on what event (page or
> > application) I should set the CurrentUICulture based on the
> > querystring, "setlang".
> >
> > Since the UICulture = "auto", I cannot utilize any of the application
> > events to set CurrentUICulture. I could use PostAcquireRequestState if
> > UICulture is not auto on in page directive.
> >
> > I cannot use page event effectively either. I tried to set
> > CurrentUICulture based on querystring in Page.PreInit. It seems that
> > if I programmatically set control's text to a resource string
> > (textbox1.text = resources.language.astring) everything works fine,
> > but if I use explicit binding declaratively on the control (<%$
> > Resources: language, astring%>), it ignores the CurrentUICulture set
> > in Page.PreInit and displays the string from the culture the page auto
> > detects. Not being able to bind declaratively is a produtivity killer
> > and therefore not acceptable.
> >
> > Can anyone shed some light on how I can accomplish this? I will repeat
> > what I want to accomplish:
> >
> > 1) UICulture = "auto" on page directive (or can I set it somewhere
> > else?)
> > 2) user selectable cultures
> > 3) being able to bind resources to control declaratively (<%$
> > Resources:
> > language, astring%>)
>
>
>

I've also got the result you mentioned on my local enviornment.
=================
if you want uiculture=auto while still
allowing user to change uiculture, the only way is to set uiculture = auto
in
web.config and not on the page. When uiculture = auto is set in web.config,
we can use application event to override it, but when uiculture=auto is set
in page directive, you cannot override it for declaratively bound resources.
================

I think the difference between the UICulture in @page directive and
web.config maybe the @Page directive's setting will be forced in some
internal time during the page's processing which makes our adjusting in
application level event be overrided. Anyway, IMO, we'd recommend that we
avoiding using the "Auto" setting together with custom culture handling ,
thus there will exist no such potiential conflict.

Thanks Steven for your reply. Yes, I think the same too, but I also think
that being able to auto select UIculture for users while allowing them to
choose ui is a very nice feature if you want pefect globalization for your
app. Thus, setting UICulture = auto in web.config seems like a good solution
to me.. are you telling me you are afraid that in the future this behavior
could change?

By the way, can you please check out this new thread of mine, titled

"reference web control in dynamically added user control, ASP.NET 2"

I am not sure how I can send you directly the URL to the post, but you
should be able to see it on the first page of this newsgroup.

En, yes, though I'm not absolutely sure whether this is changable through
different version, but since its a undocumented behavior, generally we can
not guarantee it. Anyway, I think its ok that you leave it as you currently
do.

In addition, as for the new thread you mentioned, did you just post it
right now? If so, maybe it hasn't been synchornized to our internal
program, I also search it on google and didn't find it. I'll monitor it
later. In addition, for asp.net 2.0 issue, we also suggest you try posting
in the

Share This Page

Welcome to The Coding Forums!

Welcome to the Coding Forums, the place to chat about anything related to programming and coding languages.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to ask questions about coding or chat with the community and help others.
Sign up now!