[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    typo-fixing msgids (Re: KDE_3_4_BRANCH:
From:       David Faure <faure () kde ! org>
Date:       2005-04-30 22:58:58
Message-ID: 200505010058.58819.faure () kde ! org
[Download RAW message or body]

On Sunday 01 May 2005 00:42, Krzysztof Lichota wrote:
> David Faure wrote:
> > Would it be OK with everyone if I write a script next week that can fix the msgid
> > in the .po files for each language (per Thierry Vignaud's suggestion)?
> > 
> > This would mean that when someone fixes a typo in the source, during a message freeze,
> > he would have to run the script over a full kde-i18n checkout (or ask me to do it),
> > and he should mention that fact in the commit log to avoid raising eyebrows :)
> 
> As I suggested many times earlier, I think the correct solution would be 
> to add translation with typo fix for en_US language - this way msgid 
> would not change. The same way as en_GB fixes their local spelling 
> (color vs. colour).

I think this is too much trouble and source of confusion.
And most people won't install en_US, so they'll still get the typos.

> Having said that, for fixing sources I think there will be concurrency 
> issues:
> 1. What if your script interferes with scripty? This might lead to some 
> languages having new translation and some not.

Doing an atomic over the whole of kde-i18n including the templates
will ensure that the .pot and .po file are changed together.
But indeed the problem is the change in the sources vs the kde-i18n change.

Coolo, do you see any solution for that one? Whichever one is committed
first, if scripty runs meanwhile then all translations will be marked as fuzzy.
How can we detect if scripty is currently running?

> 2. Translators tend to keep file to on their disk for a while and then 
> commit it back, replacing the contents. Then the translated message 
> would be lost.

Impossible, cvs/svn tells you when you have to update before being
able to commit, due to a commit having been made on the server.
Every time I run check_po_files, the same situation happens: someone else
than the translators is changing a .po file. Like everyone using CVS,
translators have to remember to update before starting to work, and to
commit relatively often. This is the only way people can work together.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
[prev in list] [next in list] [prev in thread] [next in thread]