In the wordpress options table (mine is called wpp_options), wp-property adds an entry called wpp_settings that has the configuration of wp-property (initial values and values that you setup via the settings page when you install the plugin).
One of this properties refers to the language the google geocoding api translates to (variable: google_maps_localization). In order to setup this property (default is en locale, which means every address you type in every language it reverse locates it and returns the data in english language), there is a dropdown box on the properties page. This means that when I choose an address to type into wp-property entry, either it’s german either it’s chinese, or in my case, greek, it will generate the reverse address (or the nearest address data) in ENGLISH. If I recheck that in greek (EL) it will translate the above addresses in greek. But the problem is that this setting is global for the wp-property.
The same thing stands for choosing your own page to override property settings. I would like for example to have a different page for english properties (whereas english I mean international), and a different page for greek properties (remark: not properties in greece, but the language of the page).
So my thoughts are that when it is detected that wpml exists (I might try to implement it myself but it seems too big work for a simple customization) it needs to do this:
1. basic fallback page (en) with all the wp-property settings set there initially.
2. for each different wpml language setup a second ruleset that is dependent on that language. for example, I have enabled greek (el, my native language) and spanish (es), which means that:
every option I do while I am in greek, will stay for the greek site only. and in spanish for the spanish site only, just like how the wpml plugin works, on posts, pages, custom types etc.