translation support for the workflow
|Reported by:||jg||Owned by:||Jonas Borgström|
Description (last modified by )
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….
Change History (7)
comment:6 by , 11 years ago
|Milestone:||0.13 → 0.12|
|Summary:||Translation facilities needed. → translation support for the workflow|