text private-message can't be translated

It would seem that if you wrapped the above variable with a t() that you would be able to
customize display right?

so:

drupal_render(t($form[$key]['type']));

Ok I have a better and actually working solution...

see attached patch

oops!

patch updated to include one more location where the string occurs.

i installed last version and the problem is still there. will this patch be ever applied to the module, please.

i wonder do wee need that column at all? every message in private messages is of private message type, isn't it? or some other types of documents also possible to send via private messages? if yes, i could not figure out how.

there is a privatemsg API for sending messages. These
could potentially be called something other than private
messages. For example on a site in development with
classified ads, we are using privatemsg as part of an ad
reply system. So the classified ad replies are sent with
privatemsg type of 'ad-reply' which is different than
regular private messages of type 'private-message'

We usually don't use t() to wrap variables or functions. This will make the pot extractor script to trigger errors. In sum, you can only use t() to wrap a plain string.

An consistent way to fix that is introducing a hook_privatemsg_types() so modules could add information for the message types they implement. E.g.:

function hook_privatemsg_types() {
  $types = array();
  $types['my-type'] = array(
    'title' => t('My type'),
    'description' => t('My type description'),
  );
  return $types;
}

Patch implementing hook_privatemsg_types() attached.

i would love to see this issue is resolved in this or other way and applied to the official release. other wise i am not sure which patch to apply to.

Sorry for pinging the participants, I am closing old issues.

This version of Privatemsg is not supported anymore, maybe it is already implemented in Privatemsg for Drupal 6 and if not, you are welcome to open a new issue for it.