This suggestion is not automatic, but perhaps some way to notify interested parties (translators) that there are strings that need their attention?
-- Darian Anthony Patrick On Dec 6, 2010, at 7:49 PM, Adam Kennedy <adamkennedybac...@gmail.com> wrote: > Is there any way we can deal with these situations better in future? > > I know I've spotted and "fixed" quite a number of cases where the use > of English is (in my opinion) dubious, or the capitalisation is > "wrong" but the meaning of the string is otherwise unchanged. > > Is there some way such changes could be made in future without > breaking the translations (or in such a way that all translations are > automatically updated to match the change)? > > Adam K > > On 5 December 2010 04:54, Claudio Ramirez <padre.clau...@apt-get.be> wrote: >> On 04/12/10 17:01, Enrique Nell wrote: >>> On Sat, Dec 4, 2010 at 4:58 PM, Claudio Ramirez >>> <padre.clau...@apt-get.be> wrote: >>>> Enrique, >>>> I just uploaded a minimal updated Spanish translation. I only added what >>>> was missing and corrected errors cuased by changes in the source files >>>> (resulting in "moved" and obsoleted translations). I hope this will >>>> reduce your work. If not, feel free to ignore my commit. >>> >>> Thanks a lot, Claudio. It sure helps. >>> >>> Enrique >> >> In case Dirk is reading: I did the same for the Dutch translation as it >> had the same kind of breakage due to changes in the sources files. >> >> Claudio >> _______________________________________________ >> Padre-dev mailing list >> Padre-dev@perlide.org >> http://mail.perlide.org/mailman/listinfo/padre-dev >> > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
