TODO: Label each "scene" with a scene number. That way, we can easily reference it later, for example, when discussion limitations in the Implementation sub-section

TODO: Mention somewhere that the system does not impose a strict parallel structure on the pages. If a change in say, English is not relevant for the French community, user can leave it untranslated, and still press the Complete Translation button. Not sure where the best place to say this is. Maybe in the Storyboard, maybe in the Implementation sub-section.

In order to illustrate how CLWE supports unconstrained collaborative authoring and editing, we now describe a detailed usage storyboard. This storyboard involves three people (John Doe, Marie Quidam and Carlo del Pueblo) who are collaboratively writing the call for paper of a conference in 3 languages simultaneously (English, French and Spanish). For simplicity sake and better readability, we assume all three of them to be trilingual but that each of them are only changing the page in their native language. Also, we assume that they all the English user interface of the software. use the software with the EnglishNote however that this is not an assumption of CLWE. The system CAN be used by people who do not know all of the site's language, and they may translate and author in more than one language. Also, they may choose to operate the system with the user interface in any language of their choice.

John Doe starts out by writing basic information about the workshop on an English page. He does this in two consecutive edits.

---

SCREENSHOT: English page with parts of the text from the BabelWiki workshop Something like:

CALL FOR PARTICIPATION

Babel Wiki Workshop: Cross-Language Collaboration

Workshop Goal

The goal of this workshop is to explore how wikis and the wiki way might impact, and be influenced by, multilingual collaboration and language work. It aims to bring together people with an interest in multilingual collaboration, as well as specialists such as translators and terminologists, and authors who hope to find ways for their work to reach other language communities.

Translation State: en_v2 = {e1, e2}, fr = None, es = None

---

At this point, Marie Quidam decides to start translating in French, eventhough she can see that this is only a very prelimniary draft. She clicks on the Translate button, enters French as the target language and specifies the name of the page in French.

---

SNAPSHOT: Screen shot of dialog for specifying the language and title of a new translation. The language should be set to French, and the Title to the French title of the actual CFP for our workshop.

Translation State: en_v2 = {e1, e2}, fr = None, es = None

---

Marie then hits the Create Translation button.

---

SNAPSHOT: Screen shot initial translation dialog. The English content is pasted into the edit field and a Translation in Progress notice is inserted at the top. Red arrows call attention to this notice. Also, to the "Partial Translation" button. The first few sentences have been translated to French

Translation State: en_v2 = {e1, e2}, fr = None, es = None

---

Notice how the system automatically pasted the content of the English page into the edit box for this new French page, and that it also inserted a Translation in progress notice at the top. Marie starts translating the page, but the phone rings. To make sure she doesn't loose her work, she saves it as a Partial Translation.

---

SNAPSHOT: The French page as it appears after the "Partial Translation" save. The "translation in progress" notice appears in a yellow box, and there is a red arrow that calls reader's attention to it. There is a "translation" box that lists EN as a better translation, and that indicates FR as being only partially up to date. There are red arrows that call the reader's attention to these two things

Translation State: en_v2 = {e1, e2}, fr = {}, es = None

---

At this point, a visitor coming to this page would see a very conspicuous "Translation in progress" notice and would know to treat it with caution. He would also see a note on the right? telling him that in contrast, the English page is up to date, so that he might go read the page there if he knows English. Notice how those simple features contribute to lifting the Enforceable timely translation assumption, by providing means to publish partially translated content without fear of misleading visitors.

Next, Marie comes back from her phone conversation and picks up translation where she left, by clicking on the updated icon (icon showing a document with right pointing arrow) beside the English page name. This time, Marie finishes the translation, erases the "Translation in progress" notice, and hits the Complete Translation button.

---

SCREENSHOT: French translation page, with all of the English text highlighted in green. In particular, we see the first two English sentence highlighted in Green, eventhough they have already been translated

Translation State: en_v2 = {e1, e2}, fr = {}, es = None

---

Here, we notice something odd. The system highlights all of the English content highlighted in Green, indicating that all of it needs to be translated. But Marie had already translated the first two English sentence. This anomaly is due to the fact that the system does not actually track which part of the text have been translated. Since Marie saved her previous translation using the Partial Translation button, the system has no way of knowing which parts of edits e1 and e2 (if any) has been translated. But this does not bother Marie, and she can easily tell that the first two sentences have already been translated and focuses on the rest of the text instead..

---

SCREENSHOT: FR page after complete translation. The page is listed as being 100% up to date, and we see En as an "equivalent" translation. Red arrows call reader's attention to those two things. The in progress notice has disappeared.

Translation State: en_v2 = {e1, e2}, fr = {e1, e2}, es = None

---

The French version is now deemed to incorporate the exact same edits as the English page, and this is reflected on the screen by the fact that the French page is now listed as being up to date, and that the English page is now listed ad being an equivalent translation.

At this point, Juan del Pueblo starts translating from the French page, but does not complete it. Notice how the Controlled language pairs assumption is lifted. Juan does not HAVE to translate from the more mainstream English language, and can use as a starting point, whichever language he feels most comfortable with (French in this case).

---

SNAPSHOT: Spanish page with only the first few sentences translated

Translation State: en_v2 = {e1, e2}, fr = {e1, e2}, es = {}

---

At this point, Marie Quidam decides to add new information to the budding CFP, and she does it in French. Note how both the Master language and the Edit freeze assumptions have been lifted. Although the CFP originally started life as an English page, Marie is allowed to make original new contributions to it in any language (French in this case). Also, eventhough the current revision of the French page is still being translated to Spanish, Marie is still allowed to modify the French page without having to wait for Spanish translation to be done.

---

SCREENSHOT: French page with new content added to it. Both English and Es are now listed as needing improvements, and red arrows call reader attention to that. The page is scrolled down to show the newly added text, which is:

Thèmes abordés

Les thèmes qui pourront être abordés dans l'atelier comprennent, sans s'y limiter:

* Méthodes de traduction collaborative
* Projets de traduction collaborative
* Élaboration collaborative de ressources de traduction
* Wikis multilingues et traduction de contenu wiki

Translation State: en_v2 = {e1, e2}, fr = {e1, e2, e3}, es = {}

---

All of a sudden, John Doe hears that the deadline for paper submissions has been advanced by a month! He feels that this is information which needs to be conveyed right now and urgently. He goes to the English page and notices that it is severly out of date compared to the French (only X% up to date). But he is in a rush and does not have time to translate from French. So she edits the English page and adds information about the sumbission deadlines. When he saves the page he checks the send urgent translation request option (that checkbox is shown in earlier Fig X)

---

SCREENSHOT: English page as it appears after the deadline information has been added. English is still listed as being out of date, but French also is listed as needing improvement. Red arrows draw reader's attention to those two things. Page content is scrolled down to show the new text which says:

Important dates

Submission deadline for Extended papers (short or full): May 3rd, 2008

Translation State: en_v2 = {e1, e2, e4*}, fr = {e1, e2, e3}, es = {}

---

At this point, both English and French include edits that the other page has not yet incorporated. In addition, edit e4 in the English page, has an urgent notice flag attached to it, as denoted by the asterisk beside it in our edit set notation. This state is reflected on the screen by the fact English is listed as being only X% up to date, and French is listed as needing improvement.

When Marie Quidam comes back to the French page, she sees that French needs updating, and that this is an "urgent" request, so she feels she should translate it right away.

---

SCREENSHOT: French page. Red arrow draw reader's attention to the "urgent translation" notice.

Translation State: en_v2 = {e1, e2, e4*}, fr = {e1, e2, e3}, es = {}

---

At this point the reader may feel that John, Marie and Juan have buried themselves into a waist deep mud pit. Indeed, none of the pages currently incorporates all the edits that need to be propagated in the different languages. In other words, there does not seem to be any stable point from which translation could easily and safely proceed from. No "pivot" version, no "solid stone" hidden underneath the "mud".

Fortunately, they don't need one. Let's see how the system can help them pull themselves effortlessly out of this apparent "mess".

First, Marie translates from English to incorporate the urgent edit about submission deadlines, and saves it as a Complete Translation.

---

SNAPSHOT: French translation screen showing only the English deadline information highlighted, and only THAT information

Translation State after Saving: en_v2 = {e1, e2, e4*}, fr = {e1, e2, e3, e4*}, es = {}

---

At this point, the French version is listed as being 100% up to date. Then, John translates from French to incorporate the list of workshop themes.

---

SNAPSHOT: English translation screen showing that both the deadline and themes information in French are highlighted.

Translation State before Saving: en_v2 = {e1, e2, e4*}, fr = {e1, e2, e3, e4*}, es = {}


Translation State after Saving: en_v2 = {e1, e2, e3, e4*}, fr = {e1, e2, e3, e4*}, es = {}

---

Here, we notice something odd. Indeed, in showing parts of the French text that need to be incorporated into the English page, the system highlights not only the list of themes which was created originally in French, but also the deadline information which was originally created in English and then translated to French. This is a particular limitation of the system which we will talk about later, but for now, suffice it to say that this does not bother John. He can quickly tell that this is a part that does NOT need to be translated, and just focuses on translating the list of workshop themes.

Finally, Juan picks up his translation from French where he left it. He sees highlighted in green, not only the edits that he had seen when he first started translating from French, but also all other edits which have been done or replicated in French since them. He finishes translating all of those and saves it as a Complete Translation

---

SNAPSHOT: Spanish translation screen showing the whole French content selected.

Translation State before Saving: en_v2 = {e1, e2, e3, e4*}, fr = {e1, e2, e3, e4*}, es = {}

Translation State after Saving: en_v2 = {e1, e2, e3, e4*}, fr = {e1, e2, e3, e4*}, es = {e1, e2, e3, e4*}

---

Et voilà! All three pages now incorporate the exact same edits, and all are displayed as being 100% up to date.

Note that the particular order in which John, Marie and Juan pulled themselves from the "mud", is not prescribe by the tool in any way. They could have done it in any number of other ways.

TODO: Need to talk a bit about which assumptions are COMPLETELY lifted versus which are PARTIALLY lifted

In this storyboard, we saw how the system helps lifting the following assumptions of traditional authoring and translation environments: Master language, Edit freeze, Enforceable timely translation and Controlled language pairs. Let us talk about the remaining three assumptions listed in the Introduction.

Throughout the storyboard, we can see how the Strong coordination assumption is lifted, because at no point in the process did the three actors need to communicate with each other, nor with any "supervising" authority. Coordination is achieved implicitly through intuitive notices that act as invitations (but not a command) to take a particular action.

Regarding the Trained translators assumpation, we can see that the users do not need to be trained to follow a rigid authoring or translation process, and that the tools are intuitive enough be used without extensive training.

Finally, regarding Separation of Authoring and Translation, we can see how the system supports easy transition from authoring to editing, and vice versa. But integration of the translation process and tools does not complicate the editing operations. Authors can still edit content largely without having to worry about where and when translation will occur.

TODO: Talk about the how the translation naturally organized itself in a somewhat "linear" EN <-> FR -> ES fashion. But that was not imposed. It just grew that way. Community could also have nautrally migrated to a pivot language structure, or a clique structure. Use figures to display those three types of structures. This is a major advantage of the approach.