[WG: I18N & L10N] SAK-23119 polish translation

DAVID ROLDAN MARTINEZ darolmar at upvnet.upv.es
Fri Jan 25 10:38:04 PST 2013


Hi Sam,

First of all, I would like to thank your appreciation. I feel more safe knowing that you are reviewing each commit. Thanks so much. ;-)

Yes, it's seems like a made a mistake, although I reverted all changes before to copy XX_pl_PL.properties bundles. Sorry very much. Unfortunately, I cannot revert this now because I'm out of the office and have left my laptop there. I'm answering from my mobile and I have no way of developing Sakai code from here. Would you mind to do it on my own, please?

I also would like to ask you attention on the process of adding new translations (not updating). I think there should be an easier process to do it. Currently, the agreed process is to group all the files on the same commit. This can lead to issues like this one as you have to review the files Eclipse detect are changed across all the tools/projects. If projects are out of sakai project (i.e. indies) then the process is even more prone to errors. If make a commit per tool/project, then it more difficult to track the issue. Your proposal of having separate checkouts sound good for me. Would you mind to add it at https://confluence.sakaiproject.org/display/I18N/How+to+Translate+Sakai?

On the other side, if some structural changes happen a report via distribution list would help. This error is also an example. Or, another one: i.e. assignment can be found at sakai-trunk or an independient module, over which one should I commit changes? I'm also not sure having been updated about this. A mail explaining this situations or, even better, documenting this at Confluence (if it isn't still there) would be really great. I can't remember if this has been done but if not, I propose doing it. This will be useful to avoid errors.

Finally, let me make you a recommendation. When you work in teams and other people has mistakes, it's better to write them in private rather than to do it in public. In my case, it doesn't matter because I think that there no shame in admitting errors (I'm human...like you) but other people can feel upset or angry, believe me.

Cheers,
   David


________________________________
De: i18n-bounces at collab.sakaiproject.org [i18n-bounces at collab.sakaiproject.org] en nombre de Sam Ottenhoff [ottenhoff at longsight.com]
Enviado el: viernes, 25 de enero de 2013 17:06
Para: i18n at collab.sakaiproject.org; cle-release-team at collab.sakaiproject.org
Asunto: [WG: I18N & L10N] SAK-23119 polish translation

David Roldán, can you take a look at your commit of the polish translation in SAK-23119?

  https://source.sakaiproject.org/viewsvn?view=revision&revision=118276

It looks like you committed a modification in ForumsEmailService.java.

I also see some oddness with xsltcharon commits here?  Did you re-add a property file to an old location for xsltcharon?  I believe Earle moved xsltcharon out of osp into portal a few months ago.  Earle, can you verify?

People who work on both code and translations: I recommend using separate local checkouts to keep your translation work and dev work separate.  In these mega commits with hundreds of property files, it's really tough to find these unintended commits.

Thanks,
Sam


More information about the i18n mailing list