Please login or register to participate.
gogobd Mar 24, 2010 11:46 AM
Dear team and developers!

We are engaging at the academy of fine arts in Vienna. Our first goal is to run two pilot projects. We are very happy that a German translation is available now, but we had to change some of the phrases. So now we would like to contribute and share our changes. How can we manage that the improved translations would get into the next release? Who should we contact and collaborate with? Could we get svn/repository access? I have helped translating "The Definitive Guide to Plone" by Andy McKay into German and hope we will be able to make more usable in German regions.
Replies (7)
dhiraj Mar 24, 2010 12:28 PM
It's awesome to hear about your progress with your implementation! Good going, please keep us informed, and let us know if you need assistance. :)

Hmm... the German translation has already been updated since the last release - have a look at and pick that up first to see if it precludes / merges well with your changes. If you built out with an SVN checkout from core ODN, then the translations are an SVN external, so you could try auto-merging with an svn update, if you wish.

If you just add a comment on[…]ing-cyn-in-translation-file someone in devel will grant you access on the translations repo and send you an email with further instructions, as well.

Are there any other ideas, suggestions or contributions that you wish to share? Do let us know if you are happy with any customizations that you've done or addons that you've integrated successfully and you think there's a chance it could benefit the rest of the Cynapse community.
gogobd Apr 01, 2010 09:54 AM
I have a question regarding the translations:
When you click an objects "Edit" tab you get a page with collapsable field sections. I think the headlines of those sections are not being translated - is that a bug?
dhiraj Apr 01, 2010 10:35 PM
We had to override quite a bit of Archetypes and CMFEditions templates to get that to work, so possibly it's translation domain related - the translation strings would simply not be included in the PO file generation in this case.

Will have a look at this soon - adding missing translation strings is important! Could you please post a screenshot of what it's looking like in your situation? It will help us compare, if nothing else. :)
gogobd Apr 02, 2010 07:52 AM
Sure I'd be happy to do so - please advide me *where* to put the screenshot.
dhiraj Apr 02, 2010 12:26 PM
You could always upload an image here into the Community. The proper thing to do is to actually create a new issue in Translations project, of course, here:[…]/new
dhiraj Apr 02, 2010 07:57 PM
I was able to reproduce the problem at my end, and have added an issue for this, here:
dhiraj Apr 02, 2010 08:58 PM
Done! :)
Isolated the problem, fixed it. The svn trunk will now pick up these translated values.
The translation files have already been updated with the 4 new strings of the section headers. You can go ahead and update the translation, but this will appear only with next release unless you include the changes from svn trunk.
Cynin Core changeset URL:[…]/3306