Download & Extend
Token » Issues

Token are not all translated correctly

Posted by srobert72 on August 11, 2009 at 7:11am
Project:Token
Version:6.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (duplicate)
Issue tags:token, translate

Issue Summary

Hi all,

Thx for your good job.

I defined my "Content Type - XXXXX" page title as :
[type-name] ~ [page-title] ~ [site-name] ([language])
[page-title] ~ [site-name] ([language]) ==> OK, they are translated
[type-name] ==> NOK, it always appears in english

Same for Taxonomy, I defined my "Vocabulary - XXXXX" page title as :
[vocab] ~ [page-title] ~ [site-name]
[page-title] ~ [site-name] ==> OK, they are translated ([cat] in [page-title] is transaletd)
[vocab] ==> NOK, it always appears in english

Did I missed something ?
How could I translated my page title completly ?

Thx a lot

Login or register to post comments

Comments

#1

Posted by srobert72 on August 11, 2009 at 7:20am
Issue tags:+token, +translate

I'd like to precise that all my ContentType names are translated with TranslationTable.
If I show Node:Type in a Node view it appears translated.
The problem is only in PageTitle.

#2

Posted by tomsm on September 29, 2009 at 7:22am

I have the same issue with the "automatic nodetitles" module.

#3

Posted by srobert72 on November 26, 2009 at 7:49pm

No one to help us ?

#4

Posted by nicholasThompson on December 2, 2009 at 12:44pm
Project:Page Title» Token
Version:6.x-2.x-dev» 6.x-1.x-dev

This sounds more like a bug with the Token module...
See:
http://drupalcode.org/viewvc/drupal/contributions/modules/token/token_no...

Note how the [type] token gets assigned the value of $node->type. Shouldn't that get passed to the t() function?

Moving to the Token module... I cant see how Page Title can solve this one considering the token at fault is being provided by the Token module.

#5

Posted by srobert72 on December 25, 2009 at 7:05pm

What is status of this issue ?

#6

Posted by srobert72 on December 31, 2009 at 2:18pm

I did another test and in fact token [type-name] fails.

Extract from Token help

Available Tokens List
[type-name] : Node type (user-friendly version)

But in fact [type-name] displays machine version.

#7

Posted by Dave Reid on March 7, 2010 at 2:38am
Status:active» closed (won't fix)

Token would have to pass those strings through t() as a variable, which is explicitly discouraged in t()'s documentation, but I've seen done elsewhere. The other option is to define a small token function that can run i18nstring.module's tt() function (for example, see #635474: Add support for i18n to translate node type names). The third option would be to define your own tokens for the translated node type.

Since core's D7 token implementation does not translate variables, I think we should put this as won't fix since #3 is the only appropriate solution.

#8

Posted by Dave Reid on March 7, 2010 at 2:39am
Status:closed (won't fix)» closed (duplicate)

Actually this is a duplicate of #305639: i18n support for the tokens?