translation support for the workflow

[jg]

Localization of the workflow state names and actions is still an open point for 0.12dev. We can use this ticket in order to discuss how to do this.

The following use case (i.e. the original feature request) can certainly be achieved using TracWorkflow (see comment:5), but would require translation of the status: someone who doesn't speak english is unlikely to understand what the proposed translation_needed status means…

---

Here's the problem: you have a bug reporter who does not speak English; and/or the bug assignee does not speak English.

It should be possible for the system to know that translation may be needed, and keep a workflow of some sort for people involved in a project to help by translating bug reports/responses/queries for information.

Concrete example: Teachers in Arahuay, the OLPC trial site in Peru, want to be able to make bug reports and enhancement requests on activities. But I don't speak Spanish, and they don't speak English. Nor do I know what languages a given maintainer can speak, so I can't predict whether a translation step will be needed. There are people in the OLPC project able/willing to help with translation, but we don't have a way to know what needs translation….

[Christian Boos]

Wrong Trac? Did you intend to file this on the ​OLPC's Trac?

[Noah Kantrowitz]

No, he means that for each ticket, someone can come along and translate it into another language. Somewhat of a tricky requirement, and my gut reaction is to try it in a plugin first to see how complex it will be.

[Christian Boos]

Well, this could be done the Wiki Way if translators had the possibility to edit the ticket description and add a translated version directly there. Currently we check for TICKET_ADMIN for doing this, but with 0.11 and #2945, it would be less problematic to require a lower privilege level for description editing, as we have full traceability of changes.

For the workflow part, it's already possible to add a translated state after the new state, see TracWorkflow.

[sid]

So is there something actionable to move this forward? Or are we saying it already can be done using TracWorkflow and TICKET_ADMIN privileges if the end-user is using 0.11?

[Christian Boos]

As sid said, this should be mostly doable using 0.11, e.g.

• add two states translation_needed, translation_needed_new similar to the infoneeded / infoneeded_new pair in the source:tags/trac-0.11rc1/contrib/workflow/opensource-workflow.ini​
• eventually add a Original Language custom field (I imagine the target language will be english, if not, a second field could be used for that)
• give your translators at least the TICKET_EDIT_DESCRIPTION permission

Localization of the workflow state names and actions is still an open point, but for 0.12dev. We can eventually use this ticket in order to discuss how to do this, as the use case presented here would nearly require this: someone who doesn't speak english is unlikely to understand what translation_needed means…

[Christian Boos]

Replying to cboos:

As sid said, this should be mostly doable using 0.11, e.g.

… so worksforme.

Localization of the workflow state names and actions is still an open point, but for 0.12dev. We can eventually use this ticket in order to discuss how to do this, as the use case presented here would nearly require this: someone who doesn't speak english is unlikely to understand what translation_needed means…

See rather #5441 for that.