Posted by vthirteen on October 25, 2009 at 10:29pm
Jump to:
| Project: | Internationalization |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
i'm sorry but i could not find the answer. is it possible to translate user profile fields? user profile is a core module that admits fields like select fields, text areas, etc. they're not translatable through the translate interface. so how are they supposed to be used in a multilingual environment?
Comments
#1
I have translated the profile fields using the translate interface. For example, when I search for the field "Last name", the translate interface shows:
Text group: profile
String: Last name, field: profile_last_name:title
Languages: fr nl
Did you "Refresh" the strings?
Flushed the caches?
#2
you're talking about the field labels, which are translatable. i'm talking about the content of the fields. think of something like:
- label: "User bio"
- content: "I have a long experience in... etc."
#3
I only translated the content of a list selection field. When I search for random content, such as a street name, using the translate interface, I cannot find anything. So I think it is not possible...
#4
No, field content is not translatable.
#5
does this mean that this module cannot be used in a multilingual website?
is it just for technical correctness (that is, not to consider field content as a translatable variable since it's user submitted and not a variable) or is there any other reason for that?
is there any other way to render user profiles in different languages besides i18n?
#6
i have core user profile module installed. user profile includes a category field (as select list). this select field is translated through i18n and in user profile pages it is displayed properly in different languages.
though when rendered in a user view this field does not change according to the current language. the maintainers of views say that it's not a problem with views but with the contributed module, that is i18n.
see for reference: http://drupal.org/node/619684
it looks like i18n lacks some implementation for user views. correct me if i'm wrong.
#7
Please, reopen only if you have a patch
#8
don't understand why "won't fix"....
anyway, in the end i disabled the core user profile module and used this module: http://drupal.org/project/content_profile
#9
@vthirteen> don't understand why "won't fix"....
Easy: It won't fix itself. I won't fix it. Will you fix it?
So, again, 'reopen only if you have a (good) patch'