On Thursday, 25 January 2007 21:31, Jasper Stein wrote: > Op donderdag 25 januari 2007 21:22, schreef Jasper Stein: > > Current stats (vs. the 1.4.0 build) are > > [...] > > So now that there's talk of making a 1.5.0 release soon here's a question: > are translations automatically taken care of (for as far as applicable) or > should I, the translator, do something about making sure the 1.4.0 > translations are not lost? I.e., how is it done, going from 1.4.0 to 1.5.0?
Now that the strings have been frozen and it has been announced, translators should pick the latest .po file from the SVN repository, and use it to translate the new and modified English strings that will be part of the new release. Once your work is done, commit the updated .po files to the repository again, or send it to the list or to the sf.net tracking system, to be included in the next release package. If you have updated the .po file from the 1.4 release, it could be used for an hypothetical 1.4.1 release but not for 1.5, sorry. There is not an automatic process to transfer your translations, except if you try to merge the changes yourself (for instance, using the po/messages.sh script). Another solution is to merge by hand the old and updated .po file over the new one, using a KBabel feature: configure your updated .po file from the 1.4 release as a PO Auxiliary (Settings->Configure Dictionary->PO Auxiliary), and then use it to search translation suggestions. Regards, Pedro ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
