I don't understand what you mean by "setSessionLocale uses the simple 2
char string to set the locale" - what makes you think that?
It would be helpful if you could list the steps taken to reproduce the
problem you are trying to describe (preferably on the demo server).
-Adrian
madppiper wrote:
Hey everyone,
while trying to localise our webstore I got a little confused over the use
of the localeString. I noticed that the setSessionLocale uses the simple 2
char string to set the locale (eg: en for English and de for German and so
on), yet sometimes the longer form of 4chars is used, ie de_DE or en_US.
Now this wouldn't really make a difference to me, but it really ruins all my
efforts to localise the content. For some reason my webstore starts with
en_US as the locale... but a click on the setSessionLocale widget changes
this to de or en respectively, hence all the lookups wouldn't work... is
this a known issue or how can i circumvent this?
