Translations for Elgg 2.0
We have created a new translation project for Elgg 2.0 at Transifex: https://www.transifex.com/elgg/elgg-core-2/
This means that translation contributors need to add missing translations into the new project. Easiest way to do this is to upload the Elgg 1.x language files to the new project and then wait until the core team pushes existing translations to the new project, and then add missing translations for any strings that were added in Elgg 2.0.
A new project is needed because the translation strings are very different between Elgg 1.x and 2.x. If we didn't add a new project, we wouldn't be able to change strings in 2.x without it affecting the strings used by 1.x. In the worst case some strings in 1.x would had gotten removed completely.
can i contribute ???? i would like to translate in hindi(india) ;)
Yes, just register an account to Transifex.
You should just do a tx push from existing translations checked into elgg to seed the translations. This way translators don't have to manually upload all the old files. Also, turn on translation memory to auto translate existing exact matches.
Ah, ok. I was wondering that there probably is an easier way.
I updated .tx/config to point to elgg-core-2 and did:
But only a couple of languages got updated: https://www.transifex.com/elgg/elgg-core-2/dashboard/
Got it figured out: The timestamp of the translations was older than the one in Transifex, so I needed to force the push.
Ok translators, Elgg 2.0 translations project now contains all the Elgg 1.x translations, but the translations for strings added in 2.0 are missing from every language.
So go ahead and start translating! :)
No, brackets are not required.
I don't know which string is in question, but maybe the original author has just thought that brackets make the translated text more readable?
E.g.
In this case the brackets are being used because the message is highly technical and the brackets make it easier to read/understand.
But use whatever you think works best in the Italian language.
Oops, that's my bad. I must have accidentally pushed the translations file of Blog plugin under the Bookmarks resource.
Yeah, I had mixed up blogs and bookmarks plugins. Now the translation resources should be correct again!
- Previous
- 1
- 2
- Next
You must log in to post replies.