Issue status update for http://drupal.org/node/19457 Project: Drupal Version: cvs Component: profile.module Category: bug reports Priority: minor Assigned to: Anonymous Reported by: stefano@tipic.com Updated by: Goba Status: active The idea is that the locale module should handle these translations, but since these are site specific, they should not be exported with the other strings when generating PO files from the site (at least not by default), and that the translation should be integarated to the admin interface (ie. some indication on the profile field name, mission statement, etc. input fields, that those are translateable, and some links pointing to the exact place). Goba Previous comments: ------------------------------------------------------------------------ March 25, 2005 - 21:19 : stefano@tipic.com The name of profile fields are not translateable, so they always appear in english in the user profile page. ------------------------------------------------------------------------ March 25, 2005 - 22:19 : hba Confirmed, I experience the same here. ------------------------------------------------------------------------ March 25, 2005 - 22:24 : Goba As it is discussed elsewhere, admin specified text is not translateable yet in Drupal, and this is generally true, like you cannot translate the site slogan or the user welcome message you specified or the flexinode type names and field names, or the admin specified menu item names. This needs some general solution, and noone provided one yet... ------------------------------------------------------------------------ March 25, 2005 - 22:44 : moshe weitzman for something like a mission statement, i wuold think we could just t() that variable and be done with it. these sorts of strings will need to be translated via the web interface, and not the PO editor ... I have never done a translation, so take my suggestions with a grain of salt.