Translating user specified strings

Confirmed, I experience the same here.

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...

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.

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).

The Internationalization module provides some general solution for this with 'language dependent variables'.

The idea is to add a language field to the variables table, and then selecting the ones with language=locale or language=null, and also caching variables by language. However, as the module is not core, it uses some workaround.

But it would be nice to have this feature in the core -it has to mess with the variable_xxx functions- and a quick solution could be to add it into the locale module. However, some better interface to manage this variables would be needed too.

In my experience there are also some other not textual ones like the site logo, that may need to be switched depending on language, when the logo image has some text.

The current policy is to not translate user supplied strings, so this is a feature request.

killes wrote this is a feature request.
I say: Absolutely, but not a minor one! For 6.0, we should come up with a generic solution for this!

Moving this to the locale component, as this is not exclusively a profile.module issue.

Oh, I missed this one and I was starting another thread about this here, http://drupal.org/node/133745
Would you mind following up there?

http://drupal.org/node/141461 is where the action is happening.