Names of content types (node types) are not translated- integrate with i18n_node

I believe that would be a token issue, not a Message's one

I have the same problem, how can I solve it , ????

Closing #2015835: [node:content-type:name] and i18n as a duplicate of this issue

i18n_node is the relevant submodule of the i18n module.

I'm not sure whether this functionality belongs in i18n or token. However, I wrote a preliminary patch for token which I tested and is working on my site, so here it is.

Works for me too, thank you! :)

Thanks ptmenny, that solves it nicely. Is this just about RTBC?

Why doesn't i18n use the API to alter token values? https://api.drupal.org/api/drupal/modules%21system%21system.api.php/func...

In patch #5, the language is not considered.
For the new version of token.token.inc ("7.x-1.5") you need something like that:

case 'content-type':
  if (module_exists("i18n_node")) {
    $type_name = i18n_node_translate_type($node->type, 'name', NULL, array('langcode' => $language_code));
  }
  else {
    $type_name = node_type_get_name($node);
  }
  $replacements[$original] = $sanitize ? check_plain($type_name) : $type_name;
  break;

[node:content-type] token will show the translated node type.

Just in case anyone lands here looking for this feature, it has been added in i18n #535522: Using translated content type from i18ncontent as a token for pathauto, which is the place to do it.

I guess this can be closed as fixed.