From: Benny M. <ben...@gm...> - 2010-11-04 19:55:11
|
Jerome, translators, Please update .po in gramps32 branch, and translate the new string in order to handle http://www.gramps-project.org/bugs/view.php?id=4301 Perhaps an English native can check my English in this long phrase, so grammer errors can be fixed before translators do their work. The strings are: _("Repair family tree?"), _( "If you click <b>Proceed</b>, Gramps will attempt to reconstruct your family tree" " from the last good backup. There are several ways this can cause unwanted" " behaviour, so <b>backup</b> the family tree first.\n" "The Family tree you have selected is stored in %s.\n\n" "Before doing a repair, verify that the Family Tree really cannot be opened" " anymore, as the database backend can recover from some errors automatically.\n\n" "<b>Details:</b> Repairing a Family Tree is actually using the last backup of" " this Family Tree, which Gramps stored on last use. If you have worked for" " several hours/days without closing Gramps, then all this information will" " be lost! If repairing fails, the original family tree will have been lost" " forever also. Hence a backup is needed. If repair fails or if you loose too" " much information on repair, you can fix the original family tree manually." " See for this the webpage\n" " http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n " "Before doing a repair, try to open the family tree in the normal manner," " several errors that can automatically be fixed can trigger the repair button." " If in this case, you can disable the repair button by removing the" " file <i>need_recover</i> in the family tree directory" ) % dirname, _("Proceed, I took a backup"), _("Stop") This extra questiondialog should stop once and for all users complaining the repair destroyed their data. Greetings, Benny |
From: Nick H. <nic...@ho...> - 2010-11-06 00:41:05
|
Benny, Your original is fairly good, but the following may read a little bit better: _( "If you click <b>Proceed</b>, Gramps will attempt to recover your family tree" " from the last good backup. There are several ways this can cause unwanted" " effects, so <b>backup</b> the family tree first.\n" "The Family tree you have selected is stored in %s.\n\n" "Before doing a repair, verify that the Family Tree can really no longer be " " opened, as the database back-end can recover from some errors automatically.\n\n" "<b>Details:</b> Repairing a Family Tree actually uses the last backup of" " the Family Tree, which Gramps stored on last use. If you have worked for" " several hours/days without closing Gramps, then all this information will" " be lost! If the repair fails, then the original family tree will be lost" " forever, hence a backup is needed. If the repair fails, or too much" " information is lost, you can fix the original family tree manually." " For details, see the webpage\n" "http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n <http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn>" "Before doing a repair, try to open the family tree in the normal manner." " Several errors that trigger the repair button can be fixed automatically." " If this is the case, you can disable the repair button by removing the" " file <i>need_recover</i> in the family tree directory." ) % dirname, _("Proceed, I have taken a backup") Regards, Nick. Benny Malengier wrote: > Jerome, translators, > > Please update .po in gramps32 branch, and translate the new string in > order to handle http://www.gramps-project.org/bugs/view.php?id=4301 > > Perhaps an English native can check my English in this long phrase, so > grammer errors can be fixed before translators do their work. The > strings are: > _("Repair family tree?"), > _( > "If you click <b>Proceed</b>, Gramps will attempt to reconstruct your > family tree" > " from the last good backup. There are several ways this can cause > unwanted" > " behaviour, so <b>backup</b> the family tree first.\n" > "The Family tree you have selected is stored in %s.\n\n" > "Before doing a repair, verify that the Family Tree really cannot be > opened" > " anymore, as the database backend can recover from some errors > automatically.\n\n" > "<b>Details:</b> Repairing a Family Tree is actually using the last > backup of" > " this Family Tree, which Gramps stored on last use. If you have > worked for" > " several hours/days without closing Gramps, then all this information > will" > " be lost! If repairing fails, the original family tree will have been > lost" > " forever also. Hence a backup is needed. If repair fails or if you > loose too" > " much information on repair, you can fix the original family tree > manually." > " See for this the webpage\n" > "http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n > <http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn>" > "Before doing a repair, try to open the family tree in the normal manner," > " several errors that can automatically be fixed can trigger the > repair button." > " If in this case, you can disable the repair button by removing the" > " file <i>need_recover</i> in the family tree directory" > ) % dirname, > _("Proceed, I took a backup"), > _("Stop") > > > This extra questiondialog should stop once and for all users > complaining the repair destroyed their data. > > Greetings, > Benny > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > ------------------------------------------------------------------------ > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2010-11-06 08:35:44
|
Ok, I changed this string as per Nick's suggestion. Jerome, can you regenerate gramps.pot please? For the translators, the text 'Proceed, I have taken a backup', is written on the OK button, so it should _NOT_ be longer than that English string. If you want to test your translation, then just create a dummy family tree, do gramps -l to see the directory of that tree, and then do in that directory: touch need_recover After that you will see the broken icon next to the family tree, and you can press the repair button to see this new dialog. Greetings, Benny 2010/11/6 Nick Hall <nic...@ho...> > Benny, > > Your original is fairly good, but the following may read a little bit > better: > > _( > "If you click <b>Proceed</b>, Gramps will attempt to recover your family > tree" > > " from the last good backup. There are several ways this can cause > unwanted" > " effects, so <b>backup</b> the family tree first.\n" > > "The Family tree you have selected is stored in %s.\n\n" > "Before doing a repair, verify that the Family Tree can really no longer be > " > " opened, as the database back-end can recover from some errors > automatically.\n\n" > "<b>Details:</b> Repairing a Family Tree actually uses the last backup of" > " the Family Tree, which Gramps stored on last use. If you have worked for" > > " several hours/days without closing Gramps, then all this information > will" > " be lost! If the repair fails, then the original family tree will be lost" > " forever, hence a backup is needed. If the repair fails, or too much" > " information is lost, you can fix the original family tree manually." > " For details, see the webpage\n" > " > http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n<http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn>< > http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn > >" > "Before doing a repair, try to open the family tree in the normal manner." > " Several errors that trigger the repair button can be fixed > automatically." > " If this is the case, you can disable the repair button by removing the" > > " file <i>need_recover</i> in the family tree directory." > ) % dirname, > > _("Proceed, I have taken a backup") > > Regards, > > > Nick. > > > Benny Malengier wrote: > >> Jerome, translators, >> >> Please update .po in gramps32 branch, and translate the new string in >> order to handle http://www.gramps-project.org/bugs/view.php?id=4301 >> >> Perhaps an English native can check my English in this long phrase, so >> grammer errors can be fixed before translators do their work. The strings >> are: >> _("Repair family tree?"), >> _( >> "If you click <b>Proceed</b>, Gramps will attempt to reconstruct your >> family tree" >> " from the last good backup. There are several ways this can cause >> unwanted" >> " behaviour, so <b>backup</b> the family tree first.\n" >> "The Family tree you have selected is stored in %s.\n\n" >> "Before doing a repair, verify that the Family Tree really cannot be >> opened" >> " anymore, as the database backend can recover from some errors >> automatically.\n\n" >> "<b>Details:</b> Repairing a Family Tree is actually using the last backup >> of" >> " this Family Tree, which Gramps stored on last use. If you have worked >> for" >> " several hours/days without closing Gramps, then all this information >> will" >> " be lost! If repairing fails, the original family tree will have been >> lost" >> " forever also. Hence a backup is needed. If repair fails or if you loose >> too" >> " much information on repair, you can fix the original family tree >> manually." >> " See for this the webpage\n" >> " >> http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n<http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn>< >> http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn >> >" >> >> "Before doing a repair, try to open the family tree in the normal manner," >> " several errors that can automatically be fixed can trigger the repair >> button." >> " If in this case, you can disable the repair button by removing the" >> " file <i>need_recover</i> in the family tree directory" >> ) % dirname, >> _("Proceed, I took a backup"), >> _("Stop") >> >> >> This extra questiondialog should stop once and for all users complaining >> the repair destroyed their data. >> >> Greetings, >> Benny >> ------------------------------------------------------------------------ >> >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a Billion" >> shares his insights and actions to help propel your business during the next >> growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > |
From: Jérôme <rom...@ya...> - 2010-11-06 10:24:15
|
> Jerome, can you regenerate gramps.pot please? done, http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=16150 Just a warning: translators need to test their translations. Current SVN is broken ! We cannot compile translations... http://www.gramps-project.org/wiki/index.php?title=Translating_GRAMPS#Save_as_.mo_file http://www.gramps-project.org/wiki/index.php?title=Translating_GRAMPS#Just_testing_your_translation Benny Malengier a écrit : > Ok, I changed this string as per Nick's suggestion. Jerome, can you > regenerate gramps.pot please? > > For the translators, the text 'Proceed, I have taken a backup', is > written on the OK button, so it should _NOT_ be longer than that English > string. > If you want to test your translation, then just create a dummy family > tree, do > gramps -l > to see the directory of that tree, and then do in that directory: > touch need_recover > > After that you will see the broken icon next to the family tree, and you > can press the repair button to see this new dialog. > > Greetings, > Benny > > 2010/11/6 Nick Hall <nic...@ho... <mailto:nic...@ho...>> > > Benny, > > Your original is fairly good, but the following may read a little > bit better: > > _( > "If you click <b>Proceed</b>, Gramps will attempt to recover your > family tree" > > " from the last good backup. There are several ways this can cause > unwanted" > " effects, so <b>backup</b> the family tree first.\n" > > "The Family tree you have selected is stored in %s.\n\n" > "Before doing a repair, verify that the Family Tree can really no > longer be " > " opened, as the database back-end can recover from some errors > automatically.\n\n" > "<b>Details:</b> Repairing a Family Tree actually uses the last > backup of" > " the Family Tree, which Gramps stored on last use. If you have > worked for" > > " several hours/days without closing Gramps, then all this > information will" > " be lost! If the repair fails, then the original family tree will > be lost" > " forever, hence a backup is needed. If the repair fails, or too much" > " information is lost, you can fix the original family tree manually." > " For details, see the webpage\n" > "http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n > <http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn> > <http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn>" > "Before doing a repair, try to open the family tree in the normal > manner." > " Several errors that trigger the repair button can be fixed > automatically." > " If this is the case, you can disable the repair button by removing > the" > > " file <i>need_recover</i> in the family tree directory." > ) % dirname, > > _("Proceed, I have taken a backup") > > Regards, > > > Nick. > > > Benny Malengier wrote: > > Jerome, translators, > > Please update .po in gramps32 branch, and translate the new > string in order to handle > http://www.gramps-project.org/bugs/view.php?id=4301 > > Perhaps an English native can check my English in this long > phrase, so grammer errors can be fixed before translators do > their work. The strings are: > _("Repair family tree?"), > _( > "If you click <b>Proceed</b>, Gramps will attempt to reconstruct > your family tree" > " from the last good backup. There are several ways this can > cause unwanted" > " behaviour, so <b>backup</b> the family tree first.\n" > "The Family tree you have selected is stored in %s.\n\n" > "Before doing a repair, verify that the Family Tree really > cannot be opened" > " anymore, as the database backend can recover from some errors > automatically.\n\n" > "<b>Details:</b> Repairing a Family Tree is actually using the > last backup of" > " this Family Tree, which Gramps stored on last use. If you have > worked for" > " several hours/days without closing Gramps, then all this > information will" > " be lost! If repairing fails, the original family tree will > have been lost" > " forever also. Hence a backup is needed. If repair fails or if > you loose too" > " much information on repair, you can fix the original family > tree manually." > " See for this the webpage\n" > "http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree\n > <http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn> > <http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tree%5Cn>" > > "Before doing a repair, try to open the family tree in the > normal manner," > " several errors that can automatically be fixed can trigger the > repair button." > " If in this case, you can disable the repair button by removing > the" > " file <i>need_recover</i> in the family tree directory" > ) % dirname, > _("Proceed, I took a backup"), > _("Stop") > > > This extra questiondialog should stop once and for all users > complaining the repair destroyed their data. > > Greetings, > Benny > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video > Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to > a Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > ------------------------------------------------------------------------ > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > <mailto:Gra...@li...> > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |