I have a site that needs to support more than one
locale. The user should be able to switch between
them from any point in the site.
No need to do anything. It is supported out of the
box. Please see the examples as well.
Well, no critique intended but I wouldn't (and didn't)
Hello,
I did some searching, but could only find info about i18n at the message
level. I am interested in i18n at the page level.
In other words, I have a site that needs to support more than one
locale. The user should be able to switch between them from any point in
the site.
This is how I
On 11/21/05, David Leangen [EMAIL PROTECTED] wrote:
Hello,
I did some searching, but could only find info about i18n at the message
level. I am interested in i18n at the page level.
In other words, I have a site that needs to support more than one
locale. The user should be able to switch
David Leangen wrote:
Hello,
I did some searching, but could only find info about i18n at the message
level. I am interested in i18n at the page level.
In other words, I have a site that needs to support more than one
locale. The user should be able to switch between them from any point in
the
Having a component on every place localized text is, doesn't seem to be
a very good solution for me. As well as not be able to localize button
captions.
The solution I've chosen was to translate the markup during parsing
(using my own modified MarkupParser). This solution works quite well for
On 11/21/05, Matej Knopp [EMAIL PROTECTED] wrote:
Having a component on every place localized text is, doesn't seem to be
a very good solution for me. As well as not be able to localize button
captions.
The solution I've chosen was to translate the markup during parsing
(using my own
