About Mandriva page

[Anne Nicolas-2]

Hi there

I've added a "about Mandriva page" which will be used in GNOME for 2010
and in KDE later.
http://svn.mandriva.com/cgi-bin/viewvc.cgi/soft/indexhtml/trunk//about/po/

fr translation is already. Regarding other languages, there is few
things to be translated. First part is
http://wiki.mandriva.com/en/Manifesto
So you can reuse existing translation in wiki

Only second part is all new


Thanks

--
Anne NICOLAS
Director of Engineering
Mandriva http://www.mandriva.com
Mandrakesoft becomes Mandriva

[Olav Dahlum-2]

Anne NICOLAS wrote:

> Hi there
>
> I've added a "about Mandriva page" which will be used in GNOME for
> 2010 and in KDE later.
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/soft/indexhtml/trunk//about/po/
>
>
> fr translation is already. Regarding other languages, there is few
> things to be translated. First part is
> http://wiki.mandriva.com/en/Manifesto
> So you can reuse existing translation in wiki
>
> Only second part is all new
>
>
> Thanks
>

A little typo:

#: index.html.in.h:4
msgid "Browse ressources"

- Olav

neljapäev, 22. oktoober 2009 13:00:03 kirjutas Anne NICOLAS:

> Hi there
>
> I've added a "about Mandriva page" which will be used in GNOME for 2010
> and in KDE later.
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/soft/indexhtml/trunk//about/po/
>
> fr translation is already. Regarding other languages, there is few
> things to be translated. First part is
> http://wiki.mandriva.com/en/Manifesto
> So you can reuse existing translation in wiki
>
> Only second part is all new
>
>
> Thanks
>

Hi,
where exactly is the text used or how one can see it? I mean, it'd be very
useful to see it in real life because just looking at the text there are some
phrases which may be translated differently depending of where they appear.

neljapäev, 22. oktoober 2009 13:00:03 kirjutas Anne NICOLAS:

> Hi there
>
> I've added a "about Mandriva page" which will be used in GNOME for 2010
> and in KDE later.
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/soft/indexhtml/trunk//about/po/
>
> fr translation is already. Regarding other languages, there is few
> things to be translated. First part is
> http://wiki.mandriva.com/en/Manifesto
> So you can reuse existing translation in wiki
>
> Only second part is all new
>
>
> Thanks
>

Hi,

I don't understand workflow. I read there was added two strings for desktop-
file but as I see in et.po there is nothing. Should I really add them
manually? I thought translation files (PO) are updated automatically as
template (POT) changes?

Marek Laane
Estonian translator

[Jani Välimaa]

Marek Laane wrote:
> I don't understand workflow. I read there was added two strings for desktop-
> file but as I see in et.po there is nothing. Should I really add them
> manually? I thought translation files (PO) are updated automatically as
> template (POT) changes?

Sync your .po manually with .pot.

msgmerge -Uv et.po index.pot

--
Jani Välimaa

kolmapäev, 28. oktoober 2009 18:12:20 kirjutas Jani Välimaa:

> Marek Laane wrote:
> > I don't understand workflow. I read there was added two strings for
> > desktop- file but as I see in et.po there is nothing. Should I really add
> > them manually? I thought translation files (PO) are updated automatically
> > as template (POT) changes?
>
> Sync your .po manually with .pot.
>
> msgmerge -Uv et.po index.pot
>

Yeah, I did that but shouldn't it be done automatically on the server side?

Marek Laane

[Mario Blättermann-2]

Am Mittwoch, den 28.10.2009, 18:19 +0200 schrieb Marek Laane:
>
> Yeah, I did that but shouldn't it be done automatically on the server side?
>
> Marek Laane
>

As far as I know, the po files from the status pages are updated daily,
but not immediately after changes in the pot template. However, other
projects (such as GNOME) have such a mechanism. The status tracker is
monitoring any Git commits, which affects the GUI or doc translation.
The appropriate files will be updated within some seconds, just as long
as the server needs to rewrite them.

Cheers,
Mario

kolmapäev, 28. oktoober 2009 20:27:11 kirjutas Mario Blättermann:

> Am Mittwoch, den 28.10.2009, 18:19 +0200 schrieb Marek Laane:
> > Yeah, I did that but shouldn't it be done automatically on the server
> > side?
> >
> > Marek Laane
>
> As far as I know, the po files from the status pages are updated daily,
> but not immediately after changes in the pot template. However, other
> projects (such as GNOME) have such a mechanism. The status tracker is
> monitoring any Git commits, which affects the GUI or doc translation.
> The appropriate files will be updated within some seconds, just as long
> as the server needs to rewrite them.
>
> Cheers,
> Mario
>

Well, status pages are not the problem - the real problem I was worried was
that template (POT) in svn was updated but not translation files (PO).
Same for doc_isos which I also resolved with manual merge but what should be
done automatically on the server.

Marek Laane
Estonian translator

[Mario Blättermann-2]

Am Mittwoch, den 28.10.2009, 20:33 +0200 schrieb Marek Laane:

> Well, status pages are not the problem - the real problem I was worried was
> that template (POT) in svn was updated but not translation files (PO).
> Same for doc_isos which I also resolved with manual merge but what should be
> done automatically on the server.
>
To update the po file should be your job. It's simple enough: Just type
»intltool-update et« to get an updated file. But imagine, the template
contains any errors, which could damage the po file. If all these
updates would made automatically in SVN, some valid files could become
unusable, if nobody take notice of it. In my mind, all changes in SVN
should be made manually. Well, I should mention an exception: Due to the
difficulty to get the current translatable strings of the rpm-summary*
modules, these files can be updated automatically, assuming the person
who does such a global update is careful and validates the result.

Cheers,
Mario

kolmapäev, 28. oktoober 2009 21:07:24 kirjutas Mario Blättermann:

> Am Mittwoch, den 28.10.2009, 20:33 +0200 schrieb Marek Laane:
> > Well, status pages are not the problem - the real problem I was worried
> > was that template (POT) in svn was updated but not translation files
> > (PO). Same for doc_isos which I also resolved with manual merge but what
> > should be done automatically on the server.
>
> To update the po file should be your job. It's simple enough: Just type
> »intltool-update et« to get an updated file. But imagine, the template
> contains any errors, which could damage the po file. If all these
> updates would made automatically in SVN, some valid files could become
> unusable, if nobody take notice of it. In my mind, all changes in SVN
> should be made manually. Well, I should mention an exception: Due to the
> difficulty to get the current translatable strings of the rpm-summary*
> modules, these files can be updated automatically, assuming the person
> who does such a global update is careful and validates the result.
>
> Cheers,
> Mario
>

Well, I strongly disagree. Integrity of template and proper updating
translation files with new/modified entries should be provider (in the case,
Mandriva's) responsibility. One of reason is that otherwise translator has
almost no way to know something is really changed.

Marek Laane
Estonian translator

[Mario Blättermann-2]

Am Mittwoch, den 28.10.2009, 21:48 +0200 schrieb Marek Laane:
>
> Well, I strongly disagree. Integrity of template and proper updating
> translation files with new/modified entries should be provider (in the case,
> Mandriva's) responsibility. One of reason is that otherwise translator has
> almost no way to know something is really changed.
>

OK, this is your opinion. But I'm more familiar with GNOME's way,
because I'm a GNOME translator. As I wrote, there is an »instant update«
at the status pages, just a few seconds after the source code change was
happened in Git. But this update doesn't affect the Git content really,
we get only an updated file from the status tracker, which we can edit
and commit at all. Mandriva lacks such an instant update, the status
pages will be updated once per day, this prevents translators from using
this pages as a »news ticker«.

Well, Mandriva has chosen for a system based on that one from KDE, and I
agree with you, in this case it's a job for the vendor to provide po
files which are up to date.

Cheers,
Mario

kolmapäev, 28. oktoober 2009 23:01:39 kirjutas Mario Blättermann:

> Am Mittwoch, den 28.10.2009, 21:48 +0200 schrieb Marek Laane:
> > Well, I strongly disagree. Integrity of template and proper updating
> > translation files with new/modified entries should be provider (in the
> > case, Mandriva's) responsibility. One of reason is that otherwise
> > translator has almost no way to know something is really changed.
>
> OK, this is your opinion. But I'm more familiar with GNOME's way,
> because I'm a GNOME translator. As I wrote, there is an »instant update«
> at the status pages, just a few seconds after the source code change was
> happened in Git. But this update doesn't affect the Git content really,
> we get only an updated file from the status tracker, which we can edit
> and commit at all. Mandriva lacks such an instant update, the status
> pages will be updated once per day, this prevents translators from using
> this pages as a »news ticker«.
>
> Well, Mandriva has chosen for a system based on that one from KDE, and I
> agree with you, in this case it's a job for the vendor to provide po
> files which are up to date.
>
> Cheers,
> Mario
>

 I've to admit  I'm absolutely not familiar with "GNOME's way". But anyway,
how can translator know something is changed if translation file is not
touched? Does it mean you have to do double work to monitor both template and
translation file?
And as for statistics (or, as you say, "status pages"), neither Mandriva nor
KDE don't display any changes in template only in translation file (well,
provided there is translation file; if not, then, of course, changes in
templates are displayed).

Marek Laane
Estonian translator

[Mario Blättermann-2]

Am Mittwoch, den 28.10.2009, 23:15 +0200 schrieb Marek Laane:

>  I've to admit  I'm absolutely not familiar with "GNOME's way". But anyway,
> how can translator know something is changed if translation file is not
> touched? Does it mean you have to do double work to monitor both template and
> translation file?
> And as for statistics (or, as you say, "status pages"), neither Mandriva nor
> KDE don't display any changes in template only in translation file (well,
> provided there is translation file; if not, then, of course, changes in
> templates are displayed).

The status tracker for GNOME works as follows:

1. Any person with write access to the Git commits a changed file.
2. The status tracker is watching any files which are referenced either
in POTFILES.in or in help/Makefile.am (for docs)
3. The changes will be merged into an existing translation from Git or
into the template, if no translation exists for a certain language.
4. The result is displayed and downloadable as plain text.
5. Translators can edit the file, upload it for review and finally
commit the new one.

All of these steps doesn't change the real content in Git, it just
happens in a »scratchpad«. Due to the permanent watch to the source code
changes, the status tracker can provide the merged po files immediately,
and we don't have to think about: »Do we already have an up-to-date
file, or don't we...?«. And it is impossible that your changed, but not
yet committed file becomes too old. Even the uploaded files will be
merged with the current pot template, if there any change was happened
in the meantime in the repository.

Additionally, the uploaded files will be tested, whether they are in
UTF-8 or contain any errors, e.g. not matching variables, such as %s in
msgid and %d in msgstr, missing mnemonics etc.

Furtherly, it prevents people with SVN access from problems with old
local copies, untracked changes etc. You do your work outside of the
SVN. Once your file is ready to commit, just type »svn up«, drag the
file into the folder, and »svn ci«. That's all.

Have a look at the environment [1], you'll see how it works.

Cheers,
Mario

[1] http://l10n.gnome.org/languages/et/gnome-2-30/ui/

neljapäev, 29. oktoober 2009 00:17:24 kirjutas Mario Blättermann:

> Am Mittwoch, den 28.10.2009, 23:15 +0200 schrieb Marek Laane:
> >  I've to admit  I'm absolutely not familiar with "GNOME's way". But
> > anyway, how can translator know something is changed if translation file
> > is not touched? Does it mean you have to do double work to monitor both
> > template and translation file?
> > And as for statistics (or, as you say, "status pages"), neither Mandriva
> > nor KDE don't display any changes in template only in translation file
> > (well, provided there is translation file; if not, then, of course,
> > changes in templates are displayed).
>
> The status tracker for GNOME works as follows:
>
> 1. Any person with write access to the Git commits a changed file.
> 2. The status tracker is watching any files which are referenced either
> in POTFILES.in or in help/Makefile.am (for docs)
> 3. The changes will be merged into an existing translation from Git or
> into the template, if no translation exists for a certain language.
> 4. The result is displayed and downloadable as plain text.
> 5. Translators can edit the file, upload it for review and finally
> commit the new one.
>
> All of these steps doesn't change the real content in Git, it just
> happens in a »scratchpad«. Due to the permanent watch to the source code
> changes, the status tracker can provide the merged po files immediately,
> and we don't have to think about: »Do we already have an up-to-date
> file, or don't we...?«. And it is impossible that your changed, but not
> yet committed file becomes too old. Even the uploaded files will be
> merged with the current pot template, if there any change was happened
> in the meantime in the repository.
>
> Additionally, the uploaded files will be tested, whether they are in
> UTF-8 or contain any errors, e.g. not matching variables, such as %s in
> msgid and %d in msgstr, missing mnemonics etc.
>
> Furtherly, it prevents people with SVN access from problems with old
> local copies, untracked changes etc. You do your work outside of the
> SVN. Once your file is ready to commit, just type »svn up«, drag the
> file into the folder, and »svn ci«. That's all.
>
> Have a look at the environment [1], you'll see how it works.
>
> Cheers,
> Mario
>
> [1] http://l10n.gnome.org/languages/et/gnome-2-30/ui/
>

It seems we had some misunderstanding. The system there seems to be roughly
same as in Mandriva or KDE. The point I raised was that changes in source code
which you could see in template (POT) were *NOT* merged in translation files
(PO) and you had to make manually "msgfmt -U language.po template.pot".

Marek Laane
Estonian translator

[Mario Blättermann-2]

Am Donnerstag, den 29.10.2009, 00:41 +0200 schrieb Marek Laane:
>
> It seems we had some misunderstanding. The system there seems to be roughly
> same as in Mandriva or KDE. The point I raised was that changes in source code
> which you could see in template (POT) were *NOT* merged in translation files
> (PO) and you had to make manually "msgfmt -U language.po template.pot".

Sorry, I've almost no experience with Mandriva translations. For now, I
was only working on translating the rpm-summary-main into German.

As far as I understand it, Mandriva provides normally merged po files in
the statistics, which contains the current changes in source code. And
the Estonian file doesn't contain changes, which are available from the
pot file. But does this mean, that these changes will be also applied in
SVN? Or are the provided (merged) po files dummy files which doesn't
affect the SVN content?

Cheers,
Mario

neljapäev, 29. oktoober 2009 00:54:38 kirjutas Mario Blättermann:

> Am Donnerstag, den 29.10.2009, 00:41 +0200 schrieb Marek Laane:
> > It seems we had some misunderstanding. The system there seems to be
> > roughly same as in Mandriva or KDE. The point I raised was that changes
> > in source code which you could see in template (POT) were *NOT* merged in
> > translation files (PO) and you had to make manually "msgfmt -U
> > language.po template.pot".
>
> Sorry, I've almost no experience with Mandriva translations. For now, I
> was only working on translating the rpm-summary-main into German.
>
> As far as I understand it, Mandriva provides normally merged po files in
> the statistics, which contains the current changes in source code. And
> the Estonian file doesn't contain changes, which are available from the
> pot file. But does this mean, that these changes will be also applied in
> SVN? Or are the provided (merged) po files dummy files which doesn't
> affect the SVN content?
>
> Cheers,
> Mario
>

AFAIK statistics page is just a frontend and not very relevant to real
translation, only reference tool (as statistics always is :.-) ). Real work
happens in SVN (or git or cvs or whatever), anyway, be it Mandriva or GNOME or
KDE or whatever.
Normally all works as it should be: some developer makes changes in the source
code->changes are extracted and put into template (POT)->translation files
(PO) are updated accordingly, introducing new untranslated strings, marking
changed strings fuzzy etc.
But in the case the process was broken and last step, i.e synchronization of
template and translation files didn't happen, whatever the reason was.

Marek Laane
Estonian translator

[Olav Dahlum-2]

Marek Laane wrote:

> neljapäev, 29. oktoober 2009 00:54:38 kirjutas Mario Blättermann:
>  
>> Am Donnerstag, den 29.10.2009, 00:41 +0200 schrieb Marek Laane:
>>    
>>> It seems we had some misunderstanding. The system there seems to be
>>> roughly same as in Mandriva or KDE. The point I raised was that changes
>>> in source code which you could see in template (POT) were *NOT* merged in
>>> translation files (PO) and you had to make manually "msgfmt -U
>>> language.po template.pot".
>>>      
>> Sorry, I've almost no experience with Mandriva translations. For now, I
>> was only working on translating the rpm-summary-main into German.
>>
>> As far as I understand it, Mandriva provides normally merged po files in
>> the statistics, which contains the current changes in source code. And
>> the Estonian file doesn't contain changes, which are available from the
>> pot file. But does this mean, that these changes will be also applied in
>> SVN? Or are the provided (merged) po files dummy files which doesn't
>> affect the SVN content?
>>
>> Cheers,
>> Mario
>>
>>    
>
> AFAIK statistics page is just a frontend and not very relevant to real
> translation, only reference tool (as statistics always is :.-) ). Real work
> happens in SVN (or git or cvs or whatever), anyway, be it Mandriva or GNOME or
> KDE or whatever.
> Normally all works as it should be: some developer makes changes in the source
> code->changes are extracted and put into template (POT)->translation files
> (PO) are updated accordingly, introducing new untranslated strings, marking
> changed strings fuzzy etc.
> But in the case the process was broken and last step, i.e synchronization of
> template and translation files didn't happen, whatever the reason was.
>
> Marek Laane
> Estonian translator
>  

Why on earth do you still discuss this? If you want statistics after
pulling an update of your local Subversion archive, use KBabel or
Lokalize. Create a project, add the directories and presto, instant
statistics. I'm using KBabel to translate both Mandriva and
OpenOffice.org and I can't really see the problem. Using the status
pages offered by e.g kiev.ua as the only pointer is plain amateurish and
to be honest, working backwards and upside down. Relying on automatic
tasks only isn't that clever either, using command line tools should be
second  to breathing for most of you. But I do really wish they would
restructure the archive in a way similar to,

http://svn.skolelinux.org/websvn/listing.php?repname=skolelinux&path=%2Ftrunk%2Fi18n%2Fopenoffice%2F#_trunk_i18n_openoffice_


Pulling statistics from this one in e.g Kbabel is like a dream compared
to the current setup I'm faced with here.

- Olav.

neljapäev, 29. oktoober 2009 17:58:58 kirjutas Olav Dahlum:

> Marek Laane wrote:
> > neljapäev, 29. oktoober 2009 00:54:38 kirjutas Mario Blättermann:
> >> Am Donnerstag, den 29.10.2009, 00:41 +0200 schrieb Marek Laane:
> >>> It seems we had some misunderstanding. The system there seems to be
> >>> roughly same as in Mandriva or KDE. The point I raised was that changes
> >>> in source code which you could see in template (POT) were *NOT* merged
> >>> in translation files (PO) and you had to make manually "msgfmt -U
> >>> language.po template.pot".
> >>
> >> Sorry, I've almost no experience with Mandriva translations. For now, I
> >> was only working on translating the rpm-summary-main into German.
> >>
> >> As far as I understand it, Mandriva provides normally merged po files in
> >> the statistics, which contains the current changes in source code. And
> >> the Estonian file doesn't contain changes, which are available from the
> >> pot file. But does this mean, that these changes will be also applied in
> >> SVN? Or are the provided (merged) po files dummy files which doesn't
> >> affect the SVN content?
> >>
> >> Cheers,
> >> Mario
> >
> > AFAIK statistics page is just a frontend and not very relevant to real
> > translation, only reference tool (as statistics always is :.-) ). Real
> > work happens in SVN (or git or cvs or whatever), anyway, be it Mandriva
> > or GNOME or KDE or whatever.
> > Normally all works as it should be: some developer makes changes in the
> > source code->changes are extracted and put into template
> > (POT)->translation files (PO) are updated accordingly, introducing new
> > untranslated strings, marking changed strings fuzzy etc.
> > But in the case the process was broken and last step, i.e synchronization
> > of template and translation files didn't happen, whatever the reason was.
> >
> > Marek Laane
> > Estonian translator
>
> Why on earth do you still discuss this? If you want statistics after
> pulling an update of your local Subversion archive, use KBabel or
> Lokalize. Create a project, add the directories and presto, instant
> statistics. I'm using KBabel to translate both Mandriva and
> OpenOffice.org and I can't really see the problem. Using the status
> pages offered by e.g kiev.ua as the only pointer is plain amateurish and
> to be honest, working backwards and upside down. Relying on automatic
> tasks only isn't that clever either, using command line tools should be
> second  to breathing for most of you. But I do really wish they would
> restructure the archive in a way similar to,
>
> http://svn.skolelinux.org/websvn/listing.php?repname=skolelinux&path=%2Ftru
> nk%2Fi18n%2Fopenoffice%2F#_trunk_i18n_openoffice_
>
>
> Pulling statistics from this one in e.g Kbabel is like a dream compared
> to the current setup I'm faced with here.
>
> - Olav.
>

Well, statistics was NOT the subject I raised. My problem was why changes in
translatable strings were not merged in translation files (PO). Honestly, I
don't know how statistics is or even could be related with this.
And I'm not so concerned for myself because I've some clues how to use gettext
but I'm concerned for normal workflow being broken (by what I mean not
synchronizing template and translation files on the server).

Marek Laane
Estonian translator

[Andrea Celli-5]

2009/10/28 Mario Blättermann <mario.blaettermann@...>:
> Am Mittwoch, den 28.10.2009, 21:48 +0200 schrieb Marek Laane:
>>
>......
>
> Well, Mandriva has chosen for a system based on that one from KDE, and I
> agree with you, in this case it's a job for the vendor to provide po
> files which are up to date.
>

For that i know,  KDE runs every night a program called "scripty" who
repairs PO files. In particular, it updates POs.
http://developer.kde.org/documentation/other/whatisscripty.php


Andrea

[Olav Dahlum-2]

Marek Laane wrote:

> neljapäev, 29. oktoober 2009 17:58:58 kirjutas Olav Dahlum:
>  
>> Marek Laane wrote:
>>    
>>> neljapäev, 29. oktoober 2009 00:54:38 kirjutas Mario Blättermann:
>>>      
>>>> Am Donnerstag, den 29.10.2009, 00:41 +0200 schrieb Marek Laane:
>>>>        
>>>>> It seems we had some misunderstanding. The system there seems to be
>>>>> roughly same as in Mandriva or KDE. The point I raised was that changes
>>>>> in source code which you could see in template (POT) were *NOT* merged
>>>>> in translation files (PO) and you had to make manually "msgfmt -U
>>>>> language.po template.pot".
>>>>>          
>>>> Sorry, I've almost no experience with Mandriva translations. For now, I
>>>> was only working on translating the rpm-summary-main into German.
>>>>
>>>> As far as I understand it, Mandriva provides normally merged po files in
>>>> the statistics, which contains the current changes in source code. And
>>>> the Estonian file doesn't contain changes, which are available from the
>>>> pot file. But does this mean, that these changes will be also applied in
>>>> SVN? Or are the provided (merged) po files dummy files which doesn't
>>>> affect the SVN content?
>>>>
>>>> Cheers,
>>>> Mario
>>>>        
>>> AFAIK statistics page is just a frontend and not very relevant to real
>>> translation, only reference tool (as statistics always is :.-) ). Real
>>> work happens in SVN (or git or cvs or whatever), anyway, be it Mandriva
>>> or GNOME or KDE or whatever.
>>> Normally all works as it should be: some developer makes changes in the
>>> source code->changes are extracted and put into template
>>> (POT)->translation files (PO) are updated accordingly, introducing new
>>> untranslated strings, marking changed strings fuzzy etc.
>>> But in the case the process was broken and last step, i.e synchronization
>>> of template and translation files didn't happen, whatever the reason was.
>>>
>>> Marek Laane
>>> Estonian translator
>>>      
>> Why on earth do you still discuss this? If you want statistics after
>> pulling an update of your local Subversion archive, use KBabel or
>> Lokalize. Create a project, add the directories and presto, instant
>> statistics. I'm using KBabel to translate both Mandriva and
>> OpenOffice.org and I can't really see the problem. Using the status
>> pages offered by e.g kiev.ua as the only pointer is plain amateurish and
>> to be honest, working backwards and upside down. Relying on automatic
>> tasks only isn't that clever either, using command line tools should be
>> second  to breathing for most of you. But I do really wish they would
>> restructure the archive in a way similar to,
>>
>> http://svn.skolelinux.org/websvn/listing.php?repname=skolelinux&path=%2Ftru
>> nk%2Fi18n%2Fopenoffice%2F#_trunk_i18n_openoffice_
>>
>>
>> Pulling statistics from this one in e.g Kbabel is like a dream compared
>> to the current setup I'm faced with here.
>>
>> - Olav.
>>
>>    
>
> Well, statistics was NOT the subject I raised. My problem was why changes in
> translatable strings were not merged in translation files (PO). Honestly, I
> don't know how statistics is or even could be related with this.
> And I'm not so concerned for myself because I've some clues how to use gettext
> but I'm concerned for normal workflow being broken (by what I mean not
> synchronizing template and translation files on the server).
>
> Marek Laane
> Estonian translator
>  

Try KBabel Catalogue Manager and you'll see my point. Everyone involved
in the translation work have probably read the articles in the wiki
anyway and very few of us, if any, lacks write access to the svn
archive, so I guess people did read after all. Anne and others do
announce their changes and we use that information for what it's worth.
Minor issues like the ones  you brought up can be fixed, but it won't
affect the work flow, unless people have some awkward way of doing
things. And if you're a coordinator it's your duty to tell and teach
people who works under your supervision. Don't get hung up in the
problem, fix it or help fixing it.

- Olav.