Pierre van Rooden wrote:
Nico Klasens schreef:
Recently, I tried to do some i19n in editors, but that did not work
well. The current ContentTag has an annoying features that it is also
a LocaleTag. When you don't explicitly set the language and/or country
then the cloud locale will always become the default MMBase locale
when the ContentYag is used as postprocessor.
It sounds like logical behavior to use the locale of the MMBase cloud
instead of (I guess?) the server locale.
Why would this be wrong?
The real annoyance is that the cloud local is reset to the server
locale. The ContentTag has this feature from the beginning so it could
have been a implementation decision :-)
Nico
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
