Translation of the captcha module from english to dutch.

It seems you based your translation on the greek translation file, which is a rather outdated now (e.g. CAPTCHA should be spelled uppercase "CAPTCHA" instead of "Captcha").
Because the strings in your po file differ to much from what is now in use, it does unfortunately not make a lot of sense to commit it.
Sorry for the work you probably put in it.

Here you find a more recent pot file:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/captcha/tra...

(Groetjes uit Gent)

I am the contributor for the Greek translation. I guess I'll have to update it for the 6.x branch (and maybe check the 5.x one). I'll do it in the next few days.

Anyway, what I'd like to say is that your work is not useless. You can use the file you created to base your correct translation. What you can do is to generate a new translation template (.pot) by using potx (if none is provided with CAPTCHA) and by using your "wrong" .po file, to copy all identical strings from the "wrong" file to the correct one. I suppose there must be a pretty good percentage of identical strings between those two files, so your work is not useless. You will only have to check the untranslated and fuzzy messages.

So, to get this done:

You use the msgmerge utility like this:

msgmerge --compendium wrong.po --no-wrap -o nl.po /dev/null new.pot

where wrong.po is the file you submitted here (it's used as template for msgmerge, the compendium parameter), nl.po is the new file that will be created and new.pot is the template file that potx generates when parsing the CAPTCHA module structure (or use the one provided with it).

Try it and see how it works. If you can't get it done, attach the template file (.pot) for the CAPTCHA module and I will do it.

Thanks GoogyX, that's an interesting pointer

I already tried it and committed an updated nl.po:
http://drupal.org/cvs?commit=107153

Yes, but there might be a few untranslated or fuzzy strings... ?

Yes, I know
I did the msgmerge trick and then went over everything to check manually.
Some fuzzy strings were very "fuzzy" ;)
and I had to change some stuff (like "CAPTCHA" instead of "captcha")

There are still some untranslated strings left, but the most visible ones are translated.

Oh ok then. I suppose esk will have to grab the file, update it for the untranslated and fuzzy strings and attach it again here.

I found this tip somewhere in the documentation pages and it works nicely. I use it to recycle old translations (for example, when new translation templates come out, I run this command to create the new .po files and fill them with the already "known" - from the old translation .po files - strings).