(added "Asynchronous translation" user stories) |
(add context) |
||
Line 6: | Line 6: | ||
= Current processes = | = Current processes = | ||
* User will connect Zanata and search for a project or group, select his language, select the document to translate and translate | |||
* User can use search and replace (even single chars) | |||
* User can use a translation memory and a glossary | |||
* User can translate a group of messages without changing page | |||
'''Strengths''': | |||
# User interface is really efficient | |||
# Search and replace is efficient | |||
# Translation memory is efficient | |||
'''Weaknesses''': | |||
# Multiple steps required to reach actual translation | |||
# No overview of activities | |||
'''Risks''': | |||
# ... | |||
'''Opportunities''': | |||
# ... | |||
= User stories = | = User stories = |
Latest revision as of 12:18, 10 August 2019
Context
The Fedora Localization Project contributors translate using a web user interface and can periodically use: command line interfaces, or file exports/imports.
Current processes
- User will connect Zanata and search for a project or group, select his language, select the document to translate and translate
- User can use search and replace (even single chars)
- User can use a translation memory and a glossary
- User can translate a group of messages without changing page
Strengths:
- User interface is really efficient
- Search and replace is efficient
- Translation memory is efficient
Weaknesses:
- Multiple steps required to reach actual translation
- No overview of activities
Risks:
- ...
Opportunities:
- ...
User stories
Translation memory:
Description | Reasons, if required | Priority |
---|---|---|
As a translator, I want to be able to query a translation memory containing a wide range of content so that knowledge beyond Fedora community is accessible.
This means: include in our translation memory translation from project out of the scope of the fedora translation community. |
. | . |
As a localization coordinator, I can automatically complete existing translation using a translation memory using manual threshold so that useless operation for translators are limited. | . | . |
As a localization coordinator, I have a tool to handle non-fedora translation content so that translation memory is continuously update. | . | . |
. | . |
Automated translation:
Description | Reasons, if required | Priority |
---|---|---|
As a translator, I get suggestion from an automation translation engine based on a wide range of content to translate faster so that translation time is reduced.
This means we have a tool we fed with our translation memory and train it to have better result. |
. | . |
As a localization coordinator, I can automatically complete existing translation using an automation translation engine manual threshold so that useless operation for translators are limited. | . | . |
As a translator, I can ask for an automated translation of a file and review suggestion so that starting a new translation is faster. | . | . |
Asynchronous translation:
Description | Reasons, if required | Priority |
---|---|---|
As a translator, I'm able to upload my translation files, so that contributing with limited internet access is possible. | . | . |
As a translator, I'm able to interact with comments made inside the translation platform with an email client, so that contributing with limited internet access is possible.
That means like a github or pagure issue, when you get a notification, you can answer directly with email. |
. | . |
As a translator, I'm able to interact with a mailing-list from the translation platform so that interaction issues with limited internet access contributors are limited. | . | . |