Safe property names may interfere with multilanguage entity csv import

[LaszloKecskes]

Multi-language entity csv import denotes languages by appending __<country_code> to the column names. Safe name creation in properties and in the csv columns substitute unsafe characters and spaces by a single underscore. The csv import relies on the column names to contain one double underscore (using split). Safe name creation can create property names with unintended double underscores.

Example: 1, Create a template with a property having a name with two consecutive unsafe characters or spaces. For example: property: subproperty. The safe name for this is going to be property__subproperty, with a double underscore. 2, Importing the following csv fails:

title, property: subproperty__hu, property: subproperty__es, property: subproperty__en
case, value_hu,value_es,value

Please note that this is an old problem that exists this since the language feature of the csv import was first implemented, and it has not occurred "in the wild", so it is probably not high priority. On the other hand, it is also most likely an easy fix.