Nico Klasens wrote: > 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. > > IMO the ContentTag should only set the locale when the attributes are > explicitly set. But before I commit this, do others agree with this?
The content-tag was originally meant to set these kind of things. Postprocessing was only an extra, because that is associated with content-type. Would it be an option to make that it does not provide a locale when it is explicitely not set? <mm:content language="" or so? Just to be a bit more backwards compatible. I think the default locale of a cloud is also the default locale of mmbase, so I don't think much people will even notice the difference. Anyhow, just my 2c. I'd say go ahead. Michiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
