Re: Re: fink-i18n digest, Vol 1 #130 - 9 msgs italian translation

Le 18 juin 2004, à 10:57, federico corazza a écrit :

>> In the beginning, I want to make a list of all the
>> files that need
>> to be translated,
You'll find the list of files that need to be translated in:

<http://micmacfr.homeunix.org/web/organisation/index.shtml.en>

at the bottom.

You should begin with the php files at the right side of the graphic. 
Only the files you see as Fr committed (the others are no longer to 
translate).

Inside this group you should begin with constants.inc. See the how to 
translate for the explanation of how to translate this file.
Then you should translate index.php.
Then you add your language to the Makefile.
Then you can commit.
Those files have a small size, so that's not a problem to distribute 
the work here. Let people decide what they want to translate, providing 
that each person tells you I want to translate this forehand, you give 
your OK or not (if someone is already on it), and then the translator 
does his/her work.

Once this first job is done, go with the xml files. Here the files are 
huge, and some are difficult to translated (more technical than 
others). So you have to decide how to translate them. What I've done 
is, I put several persons on the same file, assigning each one a given 
part of the file (i.e. some sections, no more than 100 lines for the 
most technical ones). I've sent the file in its most up-to-date version 
to the translator. He worked on it as it was. Then, as soon as he 
finished, or at the end of every week no matter he has even begun or 
the work has not been completed, he had to send me the file. I merged 
the difference manually as:
1 - the English file could have changed inbetween
2 - there can be weird translation
3 - there can be translation of tags, which, apart from some 
exceptions, should not occurred

Then, correction of misspelling with a spell tool, make check, make && 
makeinstall, re-reading on a local Apache copy so that I can catch the 
grammatical faults. Then commit. Then mail to the translator so that he 
can admire his work in action and in the same mail offer to continue 
with another file/ part of file, and so on. So I commited files part 
after part. The whole work lasted about 4 months.

When I found a translator not productive enough (i.e. no translation 
within a month), he was told that and bye, bye -:)

When I found him not skilled enough (remember the translation must flow 
as it were no translation at all), he was gracefully thanked and bye 
bye the same way.

I'm not sure a mailing list on yahoo is a good idea. This is too 
public. Personal mails, ichat, #irc channel or icq are better. What 
I've found most convenient was iChat as you can see if people are here 
and talked to them as you want, make conferences and the most important 
solve problems quickly and exchange files quickly.

Normally the one who manages, commits too. If this is not the case, the 
one who commits should have the responsability to make the tasks 1,2 
and 3 above. Then you have to be in closer relation, so that each other 
knows at any time, what is already commited, what is to be done, etc...

And I forgot to mention, when a new translator enters the team, he 
receives complete instructions about how to do the job (cvs how to, 
fink translation how to, etc...) and a list of possible translation to 
do. If he agrees with them, he chooses a file, mail the manager his 
intention, waits for approval by the manager (there can be people 
inbetween who wants to translate the same file), then when received, he 
works.

That's just my experience on this work, you could imagine any other 
solution that fits better your needs.

Michèle
<http://micmacfr.homeunix.org>