On Oct 31, 2008, at 2:05 AM, Ludovic Dubost wrote: What would be the process of committing the modified translations to our SVN with launchpad.net? Is launchpad.net customizable easily to modify that?

Some ideas of how we could integrate it with our SVN: 1) Using JIRA. Note: What they do in maven land is the following (for publishing artifacts to the central repo): * A JIRA project. * Then they have a script that reads the attached files directly from JIRA and apply them So we could have something like: * Automatically create a jira issue with a patch attached * Have a tool that reads the jira issues and apply the patches (btw this could be generic to any type of jira patches) 2) Another solution would be to use Git and merge Git branches into our svn trunk. This is very easy to do with Git. The downside is that our contributors will not be technical so Git would be too complex for them. 3) Another solution would be to have the svn commit be made directly from the web application (by a committer). This means specifying the svn password when committing for ex. 4) Another solution would to have a special SVN server or project that has no passwords for committing and it's the users who commit directly to it using a username they provide. This would send a diff email to the list (as normal) and committers would do the review and commit the changes by doing a merge. Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Ludo, I have mentioned your work on #launchpad at irc.freenode.net and the launchpad team is interested in helping out. I have an "appointment" to talk to danilos in about 2h so if you or Vincent are interested maybe that would be a good opportunity to learn more. I will report back otherwise. Some of the things you may want to think about: - There is actually already an xwiki project in launchpad that I created a long while back, danilos suggested that translation should go through there https://edge.launchpad.net/xwiki

- There is a way to group projects together in launchpad which would take care of translations for the different components, applications etc - There is an api initiative, currently in beta, which could provide an elegant way of meeting all of your requirements through mixing a launchpad backend with a lightweight xwiki app. The api could help out in automating SVN sync although it currently doesn't focus on translation features but maybe its not too hard to put some features like that on the roadmap. https://help.launchpad.net/API

To my knowledge launchpad is going to be released as open source, but is not there yet.

Luis 2008/10/31 Ludovic Dubost <ludovic(a)xwiki.com>om>:

Dare I suggest to add the fundamental requirement to support re-organization of resource-bundles? I am not sure I saw this explicitly in this list but maybe you can confirm it's there. Basically, the need is as simple as that: - version x+1 of the software is done, there's a few changes in the resources, some parts moved to other bundles - translator is contacted to work on the translation and the merge tool applies the developer bundle organization (that includes all the moves) to his (or his language) previous files - he can now work on the reorganized bundles without needing to port manually the copies I've done a command-line-tool that does just that... but I think you want a whole lot more in the description there. paul

Le 31-oct.-08 à 02:05, Ludovic Dubost a écrit : ------------------------------------------------------------------------ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Careful, I really meant give flexibility for developers to move around sections of bundles... of course without translators re-translating. That doesn't seem to be taken care of. One bad experience which made us completely disqualify 99translations which, I think, is similar to most only tools is the absence of sections and comments... e.g. "these phrases appear in this UI". This is really crucial! paul Le 04-nov.-08 à 01:23, Ludovic Dubost a écrit : ------------------------------------------------------------------------ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Le 04-nov.-08 à 02:08, Ludovic Dubost a écrit : I mean the developer *moving the key*. For example he could move it to another file, or simply to another section of the source. For the developer renaming a key, this is more difficult as you point out, but it may be worth that such an evolution tool has "automated suggestion coming from other parts" (but "please validate that suggestion you translator"). paul ------------------------------------------------------------------------ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi, I think we need to move forward and get to a decision on our approach. I've currently not been very convinced on the launchpad approach given that it seems overly complex to get our translations loaded in their system. The french translations I've been trying to load are blocked for review (see https://translations.launchpad.net/xwiki/+imports ). Also I don't see clearly where to get the source code for launchpad to have our own install if we wanted, and how complex it would be given that launchpad has many other features unrelated to translations. On the other hand, I've improved the speed of the translation app on http://l10n.myxwiki.org using counting caches and it seems to work quite well. So I would like to launch a vote to go with the XWiki translation application approach and move it to it's own wiki on l10n.xwiki.org. We also need this wiki to be UTF-8 in order to support translations in all languages. Here is my +1 for using l10n.myxwiki.org

Ludovic Ludovic Dubost wrote:

Hi, I think we need to move forward and get to a decision on our approach. I've currently not been very convinced on the launchpad approach given that it seems overly complex to get our translations loaded in their system. The french translations I've been trying to load are blocked for review (see https://translations.launchpad.net/xwiki/+imports ). Also I don't see clearly where to get the source code for launchpad to have our own install if we wanted, and how complex it would be given that launchpad has many other features unrelated to translations. On the other hand, I've improved the speed of the translation app on http://l10n.myxwiki.org using counting caches and it seems to work quite well. So I would like to launch a vote to go with the XWiki translation application approach and move it to it's own wiki on l10n.xwiki.org. We also need this wiki to be UTF-8 in order to support translations in all languages. Here is my +1 for using l10n.myxwiki.org Ludovic Ludovic Dubost wrote:

Any -1 votes ? Or should we proceed on setting up our own l10n.xwiki.org tool ? Ludovic Ludovic Dubost wrote: > Hi, > > I think we need to move forward and get to a decision on our > approach. > > I've currently not been very convinced on the launchpad approach > given > that it seems overly complex to get our translations loaded in their > system. The french translations I've been trying to load are > blocked for > review (see https://translations.launchpad.net/xwiki/+imports ). > Also I > don't see clearly where to get the source code for launchpad to > have our > own install if we wanted, and how complex it would be given that > launchpad has many other features unrelated to translations. > > On the other hand, I've improved the speed of the translation app on > http://l10n.myxwiki.org using counting caches and it seems to work > quite > well. > > So I would like to launch a vote to go with the XWiki translation > application approach and move it to it's own wiki on > l10n.xwiki.org. We > also need this wiki to be UTF-8 in order to support translations in > all > languages. > > Here is my +1 for using l10n.myxwiki.org > > Ludovic > > Ludovic Dubost wrote: > >> Hi team, >> >> I wrore a report about the different localization strategies we >> could >> have for XWiki comparing: >> >> - a simple tool Jean-Vincent wrote >> - an L10N app I started to build >> - using launchpad.net >> >> http://dev.xwiki.org/xwiki/bin/view/Drafts/Selecting+a+tool+for+managing+Lo… >> >> >> Please review and add requirements if you see requirements that have >> not been listed. I think we need to look at the applications and >> evaluate them in more details, especially to see of launchpad.net >> could work for us. >> >> Let's discuss. >> >> Ludovic