Op Vr, 2009-12-18 om 12:11 +0100 skryf Julen: > Hi people, > > After the release of Pootle 2.0, our intention is to keep Pootle > improving, and there are exciting plans for the future. > > In this aspect, the layout of the translate page can be improved and > that has been worked in the past few days. > > The current page has its limitations, and for instance, it doesn't use > all the space available horizontally, since that space is reserved for > displaying terminology entries. > > So a Virtaal approach has been taken, expanding horizontally the > elements within the unit being edited. Thus, 100% of the space is used. > > A couple of screenshots will be more helpful than my words. > > The current unit displaying all the available features: > http://img37.imageshack.us/img37/5788/tpagefull.jpg > > The current unit with less features: > http://img707.imageshack.us/img707/5562/tpagenofull.jpg > > If some features such as suggestions, alternative source language or > terminology are missing, the displayed elements take the remaining > available space. > > Also note that there is a new element being displayed, translation > memory, which for now queries a tmserver[1] of choice. This needs more > work on the backend part, but looks promising and especially useful. > > So after showing you this, we would like to hear from you what you think > about these improvements, how can we improve or what should we focus on. > Feedback, comments, in the end.
Hi Julen. Great work on this! The second screenshot refuses to open for me :-( Hopefully I can get to it later. My first impression is somewhat overshadowed by the fact that I can't clearly see what is what. I think some of the headings above the source might be too prominent relative to the emphasis on the source box. I think this might be subtle though, so I'm not too sure what this should be. Also, I'm only looking at the first screenshot - I'm pretty sure it is better in the simpler screenshot. In Virtaal I like the idea of the source, target, and again the source and target of TM suggestions to be the same width, and being aligned. It makes some types of comparison a bit easier. I think we should consider it, but I realise this might mean using more vertical space, especially when there are many short TM suggestions where the source and target can fit in on the same line. If we can have the suggestions the same width and aligned, that would be ideal, but I realise that doesn't fit in very well with the current layout. I do like the idea of the suggestions being closer to the target, since that is what they are associated with. I realise it might be difficult to optimise for all these goals. Along the same lines, I don't think a text area as wide as the whole window is very easy to work with - I think it is far wider than most users' visual range without moving their eyes/heads. So I think we should think how we can present the target and translator comments a bit shorter. If we can make the target and comment textareas a bit shorter, we might win space for the terminology, which can often end up being quite long in long units (if we can make the layout use the space in such a configuration). Just by means of comparison: How are we doing in terms of using vertical space compared to Pootle 2.0? My guess is that we are doing quite a bit better, but I'd like to have an idea of how much. This is really exciting! Thanks again for this. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/pootle-empowers-translation-teams ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
