Translation UX/Design feedback 7

The goal of this round was to test the translation editor and search in their current state of implementation, check the effect of the introduced changes in the ULS, and try the prototypes for the advanced editing features and the homepage.

Translate workflow

 * 00:25: The user is surprised because the UI is in "Nepal Bhasa" instead of "Nepali" language.
 * 02:25: The user asks about the lack of localisation for some of the parts of the UI.
 * 02:40: The user is able to identify the current message group and use the project selector to change the message group. The user comments that it may be a bit difficult to discover. Once it is used, he considers it to be "quite usable".
 * 04:20: The user tries the ULS and considers that it has "improved a lot" since the last time he used it.
 * 05:10: The user asks to install the Nepali input method which is lacking in his machine.
 * 0523: When the user is asked to use the web-based input method, the user is able to select the input language, but the input method is not working as expected. The user is able to identify ans select the input methods offered for Nepali but the layout provided is not the usual one. He makes use of the layout from http://www.madanpuraskar.org/downloads.php
 * 10:43: The user is able to provide translations and save them.
 * 11:20: The user copies and pastes parameters such as "($2)" from the source message.
 * 13:00: The user considers the new UI to be "more easier".
 * 13: 25: The user is confused by the "secondary action menu" not showing options.
 * 13:59: The user wonders whether the vertical size of the editor may make the help area scroll to make some information harder to reach.
 * 18:43: The user is asked to disable the input method. He is able to disable it, and find the settings in the ULS to enable it again. However, the menu is not immediately enabled after applying the changes.
 * 20:00: "It's quite good. I like it".

Filtering and search

 * 21:45: The user is not able to find a specific message group, search is not noticed and was not able to find it by using search.
 * 23:00: The user asks for a more direct way to close the project selector ("an X icon") but finds out that clicking anywhere can be used.
 * 24:41: The user tries to make use of the global search for filtering the list, noticing the filtering bar in the last moment.
 * 25:19: When filtering it is not clear when the filtering is in progress or it is completed since the progress bar is shown with no new results appearing.
 * 25:55: The user is able to filter using a word and provide a translation based on a suggestion.
 * 27:00: Filtering is not working for Nepali words.
 * 31:20: The user searches for a Nepali word and is able to filter by project.

Homepage

 * 35:00: The user is able to identify the purpose of the different regions of the page.

Advanced editor

 * 39:20: The user is able to discover the way to get the glossary.
 * 41:30: The percentages are properly interpreted.
 * 42:29: "It's quite impressive. Most of the times my intuition works"