How do I translate workflow state names? I am using tokens in the Workflow Extensions module for state change buttons on nodes, but cannot find where to translate the states, so on the Japanese version of my site, I have English workflow buttons (see attached screen cap). I have tried translating state names via admin/config/regional/translate/translate and poked around my workflow, but no joy. Am I missing something?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | state change names.png | 22.43 KB | matt.rad |
| workflow button translate.png | 11.58 KB | matt.rad |
Comments
Comment #1
johnvWell, I did what you did (translating state names via admin/config/regional/translate/translate), and I succeeded without a problem.
Futhermore, I did the following:
- admin/config/regional/language : add a language, next to English) (in your case Japanese)
- admin/config/regional/language/configure : check 'User' + 'Default'
- admin/config/regional/translate/translate : translate the strings.
- user/1/edit : change language of user.
Comment #2
johnvBTW,
I'm curious how you do " I am using tokens in the Workflow Extensions module for state change buttons. "
The Workflow Extensions module does not work together with Workflow version 7.x-2.x, and almost all functionality in moved into Workflow module.
For support of the tokens, the following issue is still open: #2249211: Add token support for Transition labels.
Comment #3
matt.rad commentedHi, I am very sorry, but I mislabeled this with the wrong version number.
Comment #4
matt.rad commentedI went though what you did in #1, and it didn't work for me.
If I follow your instructions, when I switch between ja/admin/config/workflow/workflow/1 and admin/config/workflow/workflow/1, say, should I see the Workflow state names translated? What I see is attached. None of the state names translate.
I posted about this in the Workflow Extensions queue too. The maintainer there is saying that it is due to the way I am using tokens.
Thanks for the ref to the token issue. I will follow there, as from what Rik has said in the thread above, it seems to be the problem.
Comment #5
johnvI'm sorry, but 1.2 is not maintained anymore.
Comment #6
matt.rad commentedDoes 7.x-2.x make Workflow Extensions redundant?
Comment #7
johnvIndeed. See #2148933-8: Check compatibility of 'workflow extensions' with 'workflow' module, version 7.x-2.0 for a list of all functionalities. I will update the project page.
Comment #8
johnvPlease re-open if necessary.