This discussion is taking place on the Pootle mailing list. Contributions are summarized below. Please share your ideas with us. :)
The translate page is much faster with Pootle 2.1. With slow internet connections, it might still be too slow for some users. Offline translation is a great solution, but we should continue to work on improving the online experience.
So one fix would be to allow users to edit more than one string on a single page, with a single Submit button at the bottom.
(Wynand) A bit of AJAX trickery will make it more bearable. Fortunately, the Virtaal project will help to improve this considerably, since it will integrate well with Pootle whilst providing a nice off-line editing experience.
A useful addition to the interface would be a last-edited time/date next to each file. Then you would know if that file had changed since you last downloaded it, or not.
Currently, the Pootle interface is not particularly intuitive. Users misunderstand the purpose of links. Even experienced users forget which one does what, or completely miss the purpose of others. Evidently our current link names aren't always easily understood.
To review, we really want to do three main things, so we'll have three sections (instead of the current stats/editing, checks, goals, assigns, etc.):
If your browser crashes, or you have to relogin or reboot for some reason, you lose your position in the file. For heavily embedded projects like OpenOffice.org, it takes you quite a while to find your position again.
Meanwhile, workarounds include learning how the Pootle link structure works.
The current search function is better than nothing. However, it doesn't distinguish by case, it runs incredibly slowly on busy serves (see Speed above) and it doesn't work well with similar strings or complex projects.
page, in a blue ribbon, along with the navigational “arrows” mentioned above. This would be easy to implement if there is some way to reference the name of the page and the mode that page is in: http://pootle.locamotion.org/af/wordpress/admin_edit.po?translate=1&view=1&pofilename=admin_edit.po&item=(and add the number from the text box to the end)
Users aren't taking to Pootle as naturally as we would wish. They also don't read docs. We lose users who have misunderstood the functions available, or not even realized they were there. Admins don't use the features we already have (e.g. msgctxt).
<p><a href="xyz">Link here</a><sup><a class="nonU" href="abc" target="_new">[?]</a></sup></p>
… with the pseudoclass a:link “nonU” defined as 50% font size and not underlined. The advantage of this is that a question mark is nearly (?) universally understood, and it will be visible yet unobtrusive.
Although we want to form a translation community, and encourage cooperation between Pootle users, anyone using the Pootle interface is working alone.
from, what kind of job you have, etc), as in fora. This information is displayed when people view the list of users for that language.
“Contact the administrator” link next to the “About this Pootle server” link at the bottom of the page. That link can be either an e-mail address or a link to a page with just the relevant contact details on it.
The word “string” is a very geeky localisation kind of term. The normal meaning of “string” would be “a line of characters joined together”. Are there better, alternative terms?
Friedel says: ” 'Unit' is the term used in XLIFF, and is very generic. It is really what we are talking about. There could be several 'segments' once we do sub-unit segmenting. 'Item' is very generic, and not really tied to anything anybody would recognise. 'Message' is very tied to l10n and feels strange when translating a document, for example - otherwise not bad.”
Samuel says: If we move to XLIFF we should start using XLIFF terminology and hope users catch on.