Translation
| Target release | |
|---|---|
| User Story | SWIK-196 - Getting issue details... STATUS |
| Document status | DRAFT |
| Date Created | |
| Document owner | |
| Designer | |
| Developers | |
| QA | |
| Work Package & deliverables | |
| Related JIRA tasks |
Summary
As a user I want the system to translate the content of existing decks and slides to another language and store the translation.
Background and goals
T2.5. Support of collaborative authoring of multilingual content: (Start M1, End M36; Lead: Fraunhofer; Participants: VUA, UPM, SOTON, Pupin, UFRJ, ATHENA, InfAI). Language is one of the main barriers to the reuse of Open Educational Resources (OER). Crowdsourcing translations will make educational content more accessible in all European languages. The main goal of the task is to enable authoring and semi-automatic translation of content in different languages and to provide tools for content synchronizaton between the versions in different languages. We will also work on internationalization and localization of the SlideWiki service itself.
D2.5 SlideWiki multi-linguality support (M18). Support of multi-linguality in both content and user interfaces for content authoring, presentation and exploration.
Assumptions
- Users will be able to select from a pre-defined list of of languages.
- Users will be able to manually or automatically translate slides.
Discussion with Ali Khalili 26/7/16
- Translation can only occur at a deck-level. individual slides can not be translated
- translation will be triggered through a UI button only active when a user in on the DeckView
- The DeckView will display the languages in which the Deck is available.
Requirements
| # | Title | User Story | Importance | Notes | JIRA |
|---|---|---|---|---|---|
| 1 | As a user I want to see what languages decks are available in | ||||
| 2 | As a user I want to be able to create a new translation of a deck | ||||
| 3 | As a user I want to be able to correct a translation of a slide |
User interaction and design
Description of fields/input/elements + validation + test scenarios
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Asked by | Outcome |
|---|---|---|
| How does translation of slides linked to the content revisioning strategy? | Abi |
Not Doing
| Feature | Status |
|---|---|
Source material for user/stakeholder feedback
Requirements (/user stories) from pilot roadmap:
Evaluation/improvements by Farid Hasanov master thesis :
Translating issues. Some minor problems occurred with the embedded Google translator.
Issue1 - size of button. First of all, the language information and ’translate’ button are small, and it requires effort to find and click them.
Metric violated: Organization.
A Possible Solution could be to move it closer to the left, near the name of the presenta- tion, and to increase the size. The new appearance would be not dissimilar to the name of a presentation and below would be the ability to change it.
Issue2 - translation from the translated copies. There is no way to translate from the translated copy of a presentation. Translation is possible only from the original.
Metric violated: Friendliness.
Source.One user brought up this issue.
Evaluation at UniBonn :
Project Partners feedback: