Re: [Freecol-translators] Betawiki

[budtse <bu...@us...>]

Niklas Laxström wrote:
> On 24/07/07, Branko Wijfjes <bra...@gm...> wrote:
>   
>> It looks good and usefull. But is there some way to identify the chages in
>> CVS this way, something like the translation report?
>>     
>
> I'm not sure what do you mean exactly. Do you mean how changes in CVS
> show up in betawiki or the opposite? Or something else?
>
> The list of messages in betawiki is always the current set of messages
> that should be translated. New messages added will show up and if some
> messages are removed, they don't show up in the list anymore. It is
> possible to show only messages which are not translated, or review
> changes or all messages against the original.
> Changes to original message contents are currently not tracked. I've
> been thinking of some kind of fuzzy markings, similar to gettext, but
> I'd like to hear opinions about this.
>
>   
I certainly agree that it looks very nice, and easier to work with then 
the plain text files.  It may also make the job of the administrators a 
bit lighter when more translators appear. 
On  the other hand i believe that, as long as this fuzzy flag is not 
implemented, changes will be overlooked.  Knowing myself, with the 
availability of such a tool i will get lazy and no longer follow up on 
the freecol-commits with the same precision as i do now (because now it 
is kind of a must).

I guess, as the database is updated directly from CVS, that all 
translations should be marked fuzzy when an existing string changes.  It 
would be nice if the initiator of the change had an option to ignore the 
change and not make anything fuzzy, just to handle spelling errors, but 
this would need to be an extra manual action.  Fuzzy strings should be 
shown in Betawiki's review mode, so the translation can be easily 
compared to the master string and the fuzzy flag can be removed if ok.

regards,
Peter