Le 02/11/2014 22:00, Jesus a écrit : > El 02/11/14 a las 19:52, Benoît Minisini escribió: >> Le 02/11/2014 18:46, Jesus a écrit : >>>> >>>> No, the problem is that I can't know if the new translations can be >>>> merged directly or not. >>>> >>>> Because some of the translations can be part of a backportable bug fix, >>>> and some others can be part of a new development feature that cannot be >>>> backported. And translations files does not like to be merged... >>>> >>>> So the translation merge must be done manually with the IDE by taking >>>> the translations files from the /trunk and import them in the >>>> /branches/3.X. It's a big job if I have to do that for the IDE, all the >>>> components projects, all the examples... >>>> >>>> I need a solution to automate that... >>>> >>> >>> Do you mean I could do it by updating 3.6 branch while maintaining trunk >>> apart with its new features? In other words, does it worth doing an >>> import of lang files only for the 3.6 branch? Or directly on 3.6.1? >> >> Everything is done on '/trunk' and '/branches/3.X'. Nothing is done >> elsewhere, except for fixing a mistake before a version release that is >> based on '/tags/3.X.Y'. > > So, to be clear, should I update /branches/3.6? That way we could have > an updated and complete Spanish translation into the upcoming 3.6.2, right?
Yes. > > In the meantime, I guess we could continue doing this "manually". That's > not a problem for me. > But it's a waste of time. If I succeed in making that tool, you will just have to translate in /trunk, and it will be automatically backported. The only case where you will have to modify /branches/3.X is if you want to modify a translation that does not exist anymore in /trunk. Regards, -- Benoît Minisini ------------------------------------------------------------------------------ _______________________________________________ Gambas-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gambas-user
