Any way of retrieving the source code is fine: either download a recent nightly source package or access it via svn.
In order to translate SC in your own language, you will need to create the resources_hu.properties file, as you have already figured it out, and begin translating the strings. If a string is not found in your file, the reference english string will be used instead.
Make sure your resources_hu.properties file can be found by SC (ie located in the same directory as resources.properties) and test your translation by running SC from the source. Check  for help.
If your system is not configured to use hungarian locales, you can force it by adding "-Duser.language=hu" to the ant command.
When you're happy with your translation, you can send it to this list. We'll commit it to svn for you. One drawback is that you'll have to send us the file again when you need to update your translation. Hopefully, pootle will make things a lot easier for all of us.
Hope this helps,
Mate P. wrote:
Could you give me a brief explanation how to do it?
Should I download a Source Code snapshot from here: http://www.sip-communicator.org/download/nightly-builds/src/, or should I register and use svn? After I created resources_hu.properties how should I commit my changes to the source tree?
Thank you for proposing your contribution to a new translation.
We are now in the process of using pootle to help us organize better our translation effort, but the stabilization of pootle 1.3 takes longer than expected. In the mean time, it doesn't mean at all that translations
are pending. You can safely start working on the hungarian
Mate P. wrote:
I'm thinking about translating SC to hungarian. I read the dev mailing list archive and saw that you were waiting for pootle 1.3. Does this mean that until the release of pootle 1.3 the translations are pending? Or what is the recommended way to translate SC at the moment?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com