Hi Dwayne (and list) :) On 11/03/2010, at 5:37 PM, Dwayne Bailey wrote: > > On Wed, 2010-03-10 at 18:25 +1030, Clytie Siddall wrote: >> Hi everyone :) >> >> I've appeared again out of the brainfog. I hope nothing ate any of you >> while I was away. ;) > > Glad to see you are on your virtual feet again :)
Thanks. It feels good to be able to participate again. Each day I hope it will continue. > >> I'm seriously impressed with the New, Improved Pootle™! The changes >> are especially shiny when you compare them with an old Pootle like >> Sympa [1]. I love the cleaner interface, the direct links from the >> main language page to start translating new/changed strings and the >> pop-out Suggestions, in particular. > > Excellent, you have Julen to thank for the shiny interface and Alaa for > lots and lots of coding on the backend. I think you'll be excited about > new things in 2.1 also :) Great work, guys!! I look forward to 2.1. > >> Although we don't expect very long strings, can Pootle expand the >> translation input field further than four or five lines when you are >> typing the translation in? I struck a very long string in an OLPC file >> (etoys), and had to move the translation to a text editor to complete >> it, because the string was much longer than the input field would >> expand (2.5 pages in a text editor!), and it was a nuisance to have to >> wriggle the text back and forth. Also, when you check what you've >> input, it's more effective to see the whole string at once. > > In an ideal world, nothing should be 2,5 pages long! Very true. I reported this string on the OLPC list, and it's now a bug for etoys. However, we are occasionally going to get significantly long strings by mistake, from hasty merges of docs, or from inexperienced maintainers. > In a more ideal > world we'd do segmentation. Another reason to make sure you tell > everybody to do Google Summer of Code with us as its a proposed > project. Segmentation rocks. I hope you get plenty of project work! > > I think we lost autoexpanding text area in the move to 2.0. Am I > correct? The field does appear to expand to about 5 lines high, but no further. Once the translation is input, the whole string is displayed, but not _during_ input. > >> In Settings, I have 100 rows and a height of 5. I really don't want >> the default input field to be bigger than 5, but I do want it to >> expand further if I have to input longer strings (or, if that's not >> possible, to have buttons to make it larger, as before) > > Try Virtaal ;) Get it working natively on OSX and I'll be first in line. ;) > It might be solved with us getting autoexpand back in if > I'm correct. But not sure that would address your 2,5 page issue. We > need better thinking on how to solve that. We can only hope that we don't get many 2,5 page strings, but we are often going to get strings longer than 5 lines, and sometimes very long strings. So we do need some way of dealing with them. from Clytie Vietnamese Free Software Translation Team ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
