Hello Scott and everybody,

Is there any plan to add content localization to property agent ?

Is there a third party module that would do that ?

Thanks

I have a hacked solution that does produce reasonable results.  Have a look here.

The implementation is pretty trivial.  For example to create a translated property description, create two custom fields, one for each language. 

In the view template or wherever the description is to be dispplayed, wrap each custom field in a SPAN, DIV or other element that has the lang attribute set to the language of the field content (e.g. lang="es-ES").

You just need to add a little jQuery to your skin to remove all the elements that have their language attribute set and that don't match the page language.

/*    jQuery("[lang][lang!='"+ jQuery("html[lang]").attr('lang')+ "']").remove();    */

There's an overhead as both descriptions have to be passed to client, but it works pretty well.

Caroig I've tested your solution, it is pretty clever and simple. That could help us help Scott with a suggestion. Coudn't that filtering be done on the server side ?

That would require an extra (optionall) property for every custom field, containing the cultureinfo (fr-FR) for example, and the content would be filtered accordingly.

At least we could get an easy content localisation for custom fields. 

Another idea I'm thinking of would be a token in the template, for example [LANG-FR]...[/LANG-FR] would be : 'only dispay this if the current site language is french. 

Scott your thoughts on these suggestions ?

Scott what do you think of adding a cultureinfo property to every custom field ?

A workaround before a full localization system.

Thanks for the new Locale token Scott.
Will it be possible to add that token to custom fields caption and options and the property label (in layout settings)?

Edit: Another template where this token will be useful is in the Header template.