Tuesday 22 February 2011 11:53:42 am - 10 replies
Introduction
At the end of this tutorial, you should be able to contribute to the eZ Publish Localization project using GIT. Localizing means adding new translations to eZ Publish, enhancing existing ones, and adding or enhancing locales (currencies, week days names, date formats, etc. ).
Tuesday 22 February 2011 4:08:04 pm
Definitely lacking instructions for wannabe translators on windows, where git cli is not nearly as used as the tortoisegit gui tool... (plus it bundles a full set of cli commands, perl and tcl! bleagh
)
as a windows and GIT user, you may have good tips to share, that we will integrate to this tutorial ?
Cheers,
Modified on Tuesday 22 February 2011 9:08:10 pm by Nicolas Pastorino
Tuesday 22 February 2011 8:52:18 pm
Do I need to wait my pull request about new triggers/events be accepted before start doing more changes? Because I think if I made a pull request again it will be in the same pull request as the one before. Anyway, I think pt-BR is ok.
Modified on Tuesday 22 February 2011 8:53:47 pm by Thiago Campos Viana
Wednesday 23 February 2011 10:48:54 am
Do I need to wait my pull request about new triggers/events be accepted before start doing more changes? Because I think if I made a pull request again it will be in the same pull request as the one before. Anyway, I think pt-BR is ok.
Not being a GIT expert, i'd say it is not possible to have two distinct pull requests from the same branch. This means that we'll have to incorporate your first one before you can emit a second one. About your initial pull request, we may not be able to integrate this at the moment, since we are nearing deep-freeze on the master branch. But right after the release this should be sorted. In case you have additions/updates to make to the pt-BR translation, let us know, we'll find a solution.
Cheers and thanks Thiago !
Saturday 26 February 2011 12:38:25 am
Just sent a pull request for the french translation : https://github.com/ezsystems/ezpublish/pull/24
What about translating extensions ? Can/Should we proceed with the same workflow to translate extensions ?
Modified on Saturday 26 February 2011 12:39:11 am by Damien Pobel
Sunday 27 February 2011 10:49:51 pm
To potential translators : translation files have not yet been updated... You need to run ezlupdate before translating extensions.
Cheers
You must be logged in to post messages in this topic!
from
