I'm currently developing an Estate Agent application that will allow total globalization for as many cultures as you would care to mention. A spin off from this was a redevelopment of the Lists Module that will allow localized entries to be registered for every List, Entry, Child...

Appologies for the translations but langauges was never my strong point. Anyway, Just wondered if anyone would be interested?

 

Rob

Thanks for the response Chris, by the look of the addition to the stored procs with the @CultureName parameter, it lloks like I'm trying to achieve the same as you guys. In short... My sister lives in Spain and sells properties on her website, at present she can only sell in english unless she creates a separate entry for each language. My aim, and I'm very nearly there is to enable her to create a single property record with just a little additional input for translated content, so that the property can be viewed in any language. Obviously I can globalize all the module stuff but what I couldn't see was a way that she could globalize her lookup lists and I didn't want to have to hard code all possible permutations for property types, features such as swimming pools, terraces, air-con, mains-electric... this list is endless. Using the globalised list she can enter the property once with a single list lookup value and presto, total globalzed content.

Regards
Rob