Hello.
When playing with EToys test project in Pootle I found some usability problem: EToys extractor of PO/POTs sometimes generate very long context comment. Pootle decides column width of online editor simply by the longest information in the first column, so screen layout become very ugly. You could see the figure by searching "Multimedia" in any language of etoys project.
It would be great if we can work around with some tweak of setting in Pootle. Or, we may want to adjust (again) our comment format if Pootle can support...
Any suggestion will be appreciated.
(need ticket for this?)
Cheers, /Korakurider
-------------------------------------- New Design Yahoo! JAPAN 2008/01/01 http://pr.mail.yahoo.co.jp/newdesign/
On Nov 27, 2007, at 4:43 , korakurider wrote:
Hello.
When playing with EToys test project in Pootle I found some usability problem: EToys extractor of PO/POTs sometimes generate very long context comment. Pootle decides column width of online editor simply by the longest information in the first column, so screen layout become very ugly. You could see the figure by searching "Multimedia" in any language of etoys project.
It would be great if we can work around with some tweak of setting in Pootle. Or, we may want to adjust (again) our comment format if Pootle can support...
Maybe we can output multiple comments, one per method?
Any suggestion will be appreciated.
(need ticket for this?)
Yes, always better to keep track of things.
- Bert -
--- Bert Freudenberg bert@freudenbergs.de wrote:
Or, we may want to adjust (again) our comment
format if
Pootle can support...
Maybe we can output multiple comments, one per method?
I actually tested it on Pootle and seems to work. search "turn off smoothing" in ja_ZZ.po (that I edited by hand and uploaded for my testing purpose)
(need ticket for this?)
Yes, always better to keep track of things.
logged as #5134.
/Korakurider
-------------------------------------- New Design Yahoo! JAPAN 2008/01/01 http://pr.mail.yahoo.co.jp/newdesign/
On Nov 27, 2007, at 12:33 , korakurider wrote:
--- Bert Freudenberg bert@freudenbergs.de wrote:
Or, we may want to adjust (again) our comment
format if
Pootle can support...
Maybe we can output multiple comments, one per method?
I actually tested it on Pootle and seems to work. search "turn off smoothing" in ja_ZZ.po (that I editedby hand and uploaded for my testing purpose)
(need ticket for this?)
Yes, always better to keep track of things.
logged as #5134.
Guess we need a second ticket for pootle itself - it's not only etoys' fault.
- Bert -
Baffled by the behavior, I double checked, only to discover that, once more, the browser-specifics seem to be the one to blame here:
- Opera = fixed width, variable height = Good - Firefox = fixed width, fixed height = ok, no big deal - MS-IE = variable width, fixed height = nasty
Something I did notice in the Etoys PO is that the comment is basically one very long, continuous string without any whitespace. A simple comma-space ', ' separator would suffice to allow IE to do a better job...
I just verified it, and the lack of whitespace is the culprit (look for 'Stop' in TamTamEdit.activity) and the result is: - Opera = fixed width, variable height = Good - Firefox = fixed width, variable height = Good - MS-IE = pseudo-fixed width, variable height = almost good (still bases the 'minimum column width' on the 'maximum non-whitespace string length')
Solution? Use a better browser? ;)
Cheers, Xavier
On Tuesday 27 November 2007 06:14, Bert Freudenberg wrote: BF> On Nov 27, 2007, at 4:43 , korakurider wrote: BF> BF> > Hello. BF> > BF> > When playing with EToys test project in Pootle I found BF> > some usability problem: EToys extractor of PO/POTs BF> > sometimes generate very long context comment. Pootle BF> > decides column width of online editor simply by the BF> > longest information in the first column, so screen layout BF> > become very ugly. BF> > You could see the figure by searching "Multimedia" in any BF> > language of etoys project. BF> > BF> > It would be great if we can work around with some tweak of BF> > setting in Pootle. BF> > Or, we may want to adjust (again) our comment format if BF> > Pootle can support... BF> BF> Maybe we can output multiple comments, one per method? BF> BF> > Any suggestion will be appreciated. BF> > BF> > (need ticket for this?) BF> BF> Yes, always better to keep track of things. BF> BF> - Bert - BF> BF> BF>
Something I did notice in the Etoys PO is that the comment is basically one very long, continuous string without any whitespace. A simple comma-space ', ' separator would suffice to allow IE to do a better job...
I have removed all spaces because a Gettext tool (like msgmerge) splits the line if there is a white space in a long comment. It made me difficult to take a diff. This is a nasty reason though.
I just verified it, and the lack of whitespace is the culprit (look for 'Stop' in TamTamEdit.activity) and the result is:
- Opera = fixed width, variable height = Good
- Firefox = fixed width, variable height = Good
- MS-IE = pseudo-fixed width, variable height = almost good (still bases the 'minimum column width' on the 'maximum non-whitespace string length')
Solution? Use a better browser? ;)
Well, The best is to fix Pootle...
Cheers, - Takashi
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
korakurider -
Takashi Yamamiya -
Xavier Alvarez