CiviCRM Community Forums (archive)

I have upgraded from 3.0.2 to 3.0.4 and see there are some changes in the dutch translation.
Over the last few versions some translations have been changed a few times.
I think - mostly with regard to field labels - some stability in the translation is needed. The users are confronted with new label-titles and will get confused.

Like: Tussenvoegsel (Middle name) has been changed to Tweede Naam (second name). First, I think this isn't a good translation and secondly the purpose of the field is now different, because the change of the label. The same goes with "Voornaam". It has been marked since version 1.X as "Titelatuur en voorletters" but now changed.

On the dutch user's group website www.civicrm.nl there is a forum where we are trying to set-up some pre-discussion on the Dutch translation. Maybe we can discus the changes there -with regards to these important primary fields - BEFORE we apply them in Pootle.

The alternative is to run one's own translation, which I think is not a good thing.

Hey,

Absolutely agree that the stability of translation is important. I got in touch with Erik from EE-atWork, who offered to coordinate Dutch translation and asked him to take part in this discussion. It's good to discuss/work out the process here, so that other translation groups can get tuned it and so we can tweak the development process/translation tools to serve stability needs best.

Thx,
m

My initial thought would be to post all suggestions for translations on the Dutch website www.civicrm.nl in the forum 'Vertalingen'. We will then agree on a reasonable timeframe (for example once every quarter? or is more often required) when a new version will be released. How does that sound?

Hallo,

ik vind ook dat stabiliteit in de vertaling belangrijk is, en dat er gewoon een vertaallijst moet zijn (met afspraken als dat first name met titels is). Dat is iets wat je duidelijk moet afspreken.

Het is vreemd dat er zomaar een groep vertalers is die zich tot officiele vertalers uitroept zonder de andere vertalers maar zelfs te benaderen. Ik pas na een nieuwe release al meer dan 2 jaar de nederlandse vertaling aan. Ik ben dan ook niet blij dat de versie in pootle niet meer gebruikt wordt via sourceforge. Het kan vast beter, maar deze versie is toch beter dan de huidige in sourceforge.
Ik kreeg de vorige week via e-mail veel meldingen over het bijwerken van de woordenlijst, dus er zijn nog veel meer mensen actief als (NL) vertaler. En dat is toch mooi.

Hello Han,
that is certainly a good thing! I do not know why they asked us to become the official translator. As far a we are concerned, it only means that we are happy to co-ordinate, and I would hope you will continue to contribute. We need you, and thank you for all your efforts so far! I have also posted a request on the Dutch site (http://www.civicrm.nl/nieuwe-vertalingstool) asking for help in testing new translation products (as soon as Piotr has told us we can). We can provide feedback so Piotr can select what helps us the most.
As far as I am concerned there should be 2 versions of Dutch translation available, one 'official' translation that is updated by the community of Dutch CiviCRM-addicts that want to help, and one that is freely available for individual use.
Erik

Sorry, my reply was in dutch because i thought it was only between the Dutch and the Belgian people. But Piotr's dutch is improving. But I am happy that everyone is busy with civicrm.
I have not saved the e-mails that i recieved last week, they were about changing the translation-list. Do you know something about that?

I have just posted a reply on the error trying to edit the navigation menu. My solution was to change the dutch translation in pootle (done). It is not possible to use quotes in name of reports, because that results in not showing the tree.

I think it is good idea to try to make a new version of the mo-file. I have made myself a few tools to help for translations.  Maybe it is a idea not only to put the mo-files in sourceforge-download but also ONE civicrm.po file (for each language).
But the po-file must be with the normal translation (volgens vertaallijst), then someone can easily make his own translation.

…to add a bit background: we’re also considering things like Drupal’s l10n_server and l10n_client framework – things like http://localize.drupal.org/node/993, http://vimeo.com/6944071 and http://screencast.com/users/yfhahn/folders/Jing/media/4e0d7103-04a4-43e8-a320-777748d03317 opened my eyes to the possibilities.

Ideally, we’d love to offload the translation work/updates/coordination to the relevant communities in full, hence our evaluation of community- and communication-oriented translating platforms.

Pootle is a webbased tool, but maybe it's much work for the programmers to keep it working and will it be better with another tool.

But I would like to have a new version of the translations in sourceforge.


Because, the changing of the name of the reports (done in pootle) will make the program is working for new installations when the users want to change the menu bar.

I have found also the reason why "Your dashboard provides a one-screen .." can not be translated. In the po-file (not only nl but also for the fr) there stands \n

the \n must be deleted in the msgid-string, then the translation is working.
This is a string on the very first page of civicrm.