Opened 17 years ago
Last modified 15 years ago
#6234 closed enhancement
Translation facilities needed. — at Initial Version
| Reported by: | jg | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | i18n workflow |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
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….
