Rosetta/bzr (was: What is an Upstream?)

[kiko at async.com.br]

On Wed, Nov 08, 2006 at 12:14:13AM +0000, Tim Morley wrote:
> Well that's certainly great to hear. My knowledge of Rosetta is  
> mostly limited to the user's perspective, so it's good to know  
> there's more to the back end than might be inferred from the visible  
> front end.

Some of the functionality is hard to expose in a good manner, and some
of it is just us not getting around to doing things that are important
to you.

> >Christian:
> >So from this paragraph, for a checklist of features that you'd like to
> >be able to better manage translations:
> >
> >    - Who contributed an approved translation (implemented)
> 
> Yes, definitely; I believe this information is already recorded, but  
> I need to be able to use it too.

Does the current display at

    https://launchpad.net/distros/ubuntu/dapper/+source/kdebase/+pots/kdesktop/eu/10/+translate

serve your purposes? I'm talking about the text saying

     Translated by:          marcos on 2006-04-05 10:06:10 UTC

for the record.

> >    - Who approved a contributed translations (to be rolled out  
> >next week)
> 
> Yes.

We'll have this online shortly, and when we do you'll have similar UI to
tell this.

> >    - Whether the translation should be reviewed or not (implemented)
> 
> Well, I'm not too bothered about a binary setting that says "Needs  
> review/doesn't need review", although it would have its uses. What  
> I'm more concerned about is the next item:

Well, I think it's useful if used in combination with a whiteboard; that
way you can easily filter on messages that need to be reviewed and have
the contextual data that tells you wtf is going on there. :-)

Should the whiteboard be editable by anyone? There are pros and cons to
that approach, and I'm not sure what the right solution is.
Alternatively we could have a set of individual comments, but they could
only really be rendered in the zoomed view unless we did some fancy JS
expansion. I guess that's true of the whiteboard too, though.

> >    - Translator notes/whiteboard for each string (planned but not
> >      implemented)
[...]
> That's important! What we're having to do with the .po files we've  
> got from Rosetta is to go through and retro-fit all such comments as  
> we proof-read, and it's taking bloody ages to do from memory;  
> basically we're having to repeat all sorts of research to re-discover  
> why we chose a particular word or phrase.

So this whiteboard, it would be added to the pofile export as hashed-out
comments? Is that how you see it working? Would individual comments
added to the file be a better match?

> >Perhaps that in addition to a whiteboard?
> 
> Definitely, even if the "whiteboard" just takes the form of comments  
> in the .po file. That in fact *would* be sufficient (and would have  

Well, comments in the .po file and also in the web UI, right?
-- 
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331