Supported Use Cases

At the very beginning, a Site Admin will Configures the Site to Support Content in Multiple Languages.

Later on, a Page Author will Create a Page in a Particular Language.

Later on still, a Page Translator will Do the Initial Translation of a Page into a Given Language, or might Associate a Page to Its Existing Translation.

At some later point, a Site Visitor will Set language preferences for the site, or in her browser.

The Site Visitor will View a Page in Preferred Language, and Become Aware that the Site is Multilingual.

The Site Visitor may at some point Switch to Another Language Version of a Page if she suspects that the other language version is better or more up to date.

Todos

Note from AD: As I think of this more, I think that L-P should not worry about most of the todos for Iteration 0, because they are simple things that most of us on the team could do (even people who are not that familiar with the PhP code). Maybe L-P should focus right away on the harder todos of Iteration 1?

User Task: Configures the Site to Support Content in Multiple Languages

• I18n Setup screen
  • Language caption should say something like Default language
• * Best Language caption say Show pages in user's preferred language
• * Reg users can change the language should say Other supported languages. Also, is the checbox needed at all? If the site supports multiple languages, don't you always want to allow users to specify language preferences?
  • BUG: After Marc L did an upgrade of Tiki (to 1.10) on the wiki-translation site, it turns out that as soon as you visit a unilingual page, the list of languages that can be set for the site only has that one language in it.

Status: unassigned.

User Task: Create a Page in a Particular Language

* Q: When save a newly created page, language is by default Unknown.
* Would it be better if it was the main language of the site? Or the preferred language of the user?

Status: Unassigned

User Task: Create a Page in a Particular Language

* Normal edit dialog does the trick
* Nothing special to do.

Status: Nothing to do

User Task: Do the Initial Translation of a Page into a Given Language

* In 1.10, the Translate link on a page written in say, English, allows you to specify a language, say French, and its name in French.
* This is OK as a start, but see proposed improvements in Iteration 1.
* For now, all that needs to be done is to reword and reorganise the dialog to make it easier to use.

User Task: Associate a Page to Its Existing Translation

* Seems to be working fine

Status: Nothing to do.

User Task: Set language preferences

* User goes into Preferences menu of the Tiki site.
* Or, he can do it in Firefox.
* The Tiki preferences override Firefox preferences.
* Does the trick for bilingual visitors, may need to support tri+ lingual visitors, by having a pecking order of 2 or more preferred languages. Left for later iteration.

Status: Nothing to do

User Task: Become Aware that the Site is Multilingual.

Discussion

* At the top of each page, you have a drop down list of languages.
* TODO: Need to make sure that this drop list is ALWAYS PROMINENTLY DISPLAYED, no matter what template is used.
* Should it be a drop down list, because you only see one language at a time and it's not clear that it's multilngual.
* On the other hand, if you have 10 languages, it takes lots of real estate.
* Maybe up to 3 languages displayed, with a forth "Other".
* Should not be confusable with the system language drop down (i.e. language that the menus are displayed in).
* TODO: Evaluate and possibly implement alternative presetnations of the language list.


Status: Unassigned

User Task: Switch to Another Language Version of a Page

* That's just picking a language from the drop down list.

Status: Nothing to do.