Sorry about the late reply, but I've been very busy with things.
On Wed, 2009-09-30 at 11:56 +0200, Chusslove Illich wrote:
> (A KDE translator here.)
>
> > [: Philip Withnall :]
> > [...] My suggestion would be to translate strings to review them, and
> > discuss them (or explain any fixes) in the comment field for each string.
> > [...]
> > I think the main obstacle to people reviewing strings is the time it takes
> > to effectively duplicate the work you've just done in editing a PO file
> > when adding a bug to Bugzilla. I know that has put me off filing bugs
> > about string issues before. How about a post-commit git hook [...]
>
> I entirely agree. In fact, for quite some time I'm adding special-format
> translator comments with such notes, in hopes that one day I or someone else
> will get to harvest them in this way. Therefore I'd be most interested in
> any concrete code that comes out of your effort, to adapt it to KDE's VCS
> and reporting infrastructure.
Since nobody's replied, it's obviously not as popular an idea as I'd
thought. I'd like to get more opinions about the idea before working on
anything.
> As for design, I'd advise that the comment-to-report setup is used for more
> than just review, and to be available to all translators. For example, I use
> three types of such comments, with prefix syntax:
>
> # A plain translator comment.
> # >> Suggestion to add/modify context (msgctxt/extracted comment).
> # >! Suggestion to modify the message proper (msgid).
> # >? Something not clear, request for explanation.
> msgid "..."
> msgstr "..."
That sounds sensible.
> After your example I can see how an optional username could be good too,
> e.g. to be able to give more weight to reports from certain people ("this
> person is native-speaker reviewer, be sure to handle his reports first"). On
> the other hand, perhaps it would be enough to simply assign higher priority
> to reports from en_GB POs.
I wouldn't rely on the fact that the current batch of en_GB translators
are a little anal retentive; best to just have a meritocracy based on
username.
> One conceptual obstacle I have so far is how to handle removal of comments
> once they have been processed, to what extent can it be automatized (which
> is also linked to how to avoid repeated reports).
That could easily be done in the post-commit hook, where it would
replace them with a bug number. This would ensure that we didn't get
duplicate bug reports, too.
Philip
Attachment:
signature.asc
Description: This is a digitally signed message part