Custom profile fields are "strict" on the language: for example the gender icon depends on the value of the field (i.e. the text displayed).
There are two main problems here:
- it's not possible to have localized fields,
- when the text is changed, it requires to add also the corresponding CSS in order to fix the CSS classes that in the meantime have changed.
Point 1 could be lower priority since one language may be enough "for the time being".
Point 2, though, is a bit more pressing, because it adds a burden to the user using the custom fields.
For point 2, what I would like to do is add a "key" associated to the value, this key will replace the "value" for all the technical uses (i.e. anything except the display of the actual text to the users in the template).
Problems may be:
- how to define the key in the admin panel,
- regressions.
On top of that solution (at some point) we may be able to build a localization feature for the custom profile fields, but this may be for 2.0.
Custom profile fields are "strict" on the language: for example the gender icon depends on the value of the field (i.e. the text displayed).
There are two main problems here:
Point 1 could be lower priority since one language may be enough "for the time being".
Point 2, though, is a bit more pressing, because it adds a burden to the user using the custom fields.
For point 2, what I would like to do is add a "key" associated to the value, this key will replace the "value" for all the technical uses (i.e. anything except the display of the actual text to the users in the template).
Problems may be:
On top of that solution (at some point) we may be able to build a localization feature for the custom profile fields, but this may be for 2.0.