Hi all, The problem with alphabetical order is that potential merging conflicts may arise, as Jim suggest. However, I agree with Mungo: it's a simple way to find new keys when comparing files. I would suggest to always add new keys at the end of English file and procced with new issues needing message display at follows. Suppose there is issue, JAL-XYZ, that needs to show message ABC to the user. In the fix, we must include at the end of Messages.properties the line: label.a_b_c = ABC and also the involved code. Before to release a new Jalview version, and once features have been frozen, I would open a new issue with the transalation and localization component named "<language> translation for Jalview release N.M.P" and the review Messages_XX.properties related with <language>. If new keys are at the end of the file adding them to the language bundle should be quite straightforward. Anyway, a Java app comparing languge bundles with English file to check which keys are missing it is also easy to do. I can do it and include it under a new package at source (how about src/tools/i18n?). Cheers, David El 10/10/2014 16:57, "James Procter" <[email protected]> escribió:
> Can it be done automatically ? (ie as a formatting process ?) Otherwise > its a PITA since conflicts will happen. > > J. > > > > J. B. Procter. Jalview coordinator. > Barton group. College of life sciences. > University of Dundee. > > ----- Reply message ----- > From: "Mungo Carstairs" <[email protected]> > Date: Fri, Oct 10, 2014 15:34 > Subject: [Jalview-dev] Spanish Translation > To: "Jalview Development List" <[email protected]> > > Suggestion: > > Should we keep the contents of the Messages_x.properties sorted in > alphabetical order? > > This would make it much easier to compare versions, avoid duplicates etc. > > Any drawback? > > > Mungo > ------------------------------ > *From:* [email protected] <[email protected]> > on behalf of Jim Procter <[email protected]> > *Sent:* 10 October 2014 14:06 > *To:* Jalview Development List > *Subject:* Re: [Jalview-dev] Spanish Translation > > thanks David - it would have been better if you pushed these to the > 2_8_2_i18n branch, just so we can keep you fed with new GUI elements to > translate by merging *from* the 2_8_2 release branch ! No matter.. > > j. > > On 10/10/2014 12:41, David Roldán Martínez wrote: > > Hi all, > > I'm glad to announce that Spanish translation is ready and commited at > release_2_8_2 branch. > > Anyway, I'm not an advanced Jalview user so I'd appreciate if other > Spanish speaking user review my translations to check if they says what it > is supposed to say. Context is very important in translations and high > technical translations are very difficult because of that. Thus, double > checking can't be bad. If there is any volunteer, please, send me a private > mail and let's see how to get coordinated so that relase deadline can be > acomplished. > > Happy to see Jalview speaking Spanish! :) > > Cheers, > David > > > _______________________________________________ > Jalview-dev mailing > [email protected]http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev > > > > The University of Dundee is a registered Scottish Charity, No: SC015096 > > The University of Dundee is a registered Scottish Charity, No: SC015096 > > _______________________________________________ > Jalview-dev mailing list > [email protected] > http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev > >
_______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
