Sorry for quoting the entire digest anyway the bug in de.po fixed by Steffen http://i18n.debian.org/l10n-pkg-status/b/boinc.html
is not only in de, but on ru too ru.po:371 so would be nice for the russian translator to fix it too. thanks Gianfranco ----- Messaggio originale ----- > Da: "[email protected]" <[email protected]> > A: [email protected] > Cc: > Inviato: Mercoledì 29 Maggio 2013 1:08 > Oggetto: boinc_dev Digest, Vol 108, Issue 20 > > Send boinc_dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of boinc_dev digest..." > > > Today's Topics: > > 1. 7.1.2 compile failed at a stable Gentoo Linux (Toralf F?rster) > 2. Re: [patch] .po files with issues (Rom Walton) > 3. Re: [patch] .po files with issues (Christian Beer) > 4. Re: 7.1.2 compile failed at a stable Gentoo Linux (David Anderson) > 5. could the git comment be more descriptive or better empty ? > (Toralf F?rster) > 6. Re: could the git comment be more descriptive or better empty > ? (David Anderson) > 7. Re: could the git comment be more descriptive or better empty > ? (Jorden van der Elst) > 8. Re: could the git comment be more descriptive or better empty > ? (Charlie Fenton) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 May 2013 17:22:24 +0200 > From: Toralf F?rster <[email protected]> > To: "[email protected]" <[email protected]> > Subject: [boinc_dev] 7.1.2 compile failed at a stable Gentoo Linux > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Are the html sources are now mandatory in 7.1.2 ? > (7.1.1 worked fine using the same build system) > > * Running autoheader ... > [ ok ] > * Running automake --add-missing --copy --foreign ... > [ !! ] > > * Failed Running automake ! > > > > > # cat /var/tmp/portage/sci-misc/boinc-7.1.2/temp/automake.out > ***** automake ***** > ***** PWD: /var/tmp/portage/sci-misc/boinc-7.1.2/work/boinc-7.1.2 > ***** automake --add-missing --copy --foreign > > configure.ac:51: installing `./compile' > configure.ac:18: installing `./missing' > api/Makefile.am: installing `./depcomp' > configure.ac:952: required file `html/Makefile.in' not found > Makefile.am:16: required directory ./html does not exist > > > -- > MfG/Sincerely > Toralf F?rster > pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 > > > ------------------------------ > > Message: 2 > Date: Tue, 28 May 2013 11:46:49 -0400 > From: "Rom Walton" <[email protected]> > To: "Steffen M?ller" <[email protected]>, > "Christian Beer" > <[email protected]> > Cc: [email protected] > Subject: Re: [boinc_dev] [patch] .po files with issues > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="UTF-8" > > Christian, > > Could you apply these changes to http://boinc.berkeley.edu/translate? > > If we just commit them to the source tree, they will be overwritten the next > time we pull from the translation system. > > ----- Rom > > -----Original Message----- > From: boinc_dev [mailto:[email protected]] On Behalf Of > "Steffen M?ller" > Sent: Friday, May 24, 2013 5:11 PM > To: [email protected] > Subject: [boinc_dev] [patch] .po files with issues > > Hello, > > Debian performs a routine check on the .po files in all its packages. The one > of > BOINC http://i18n.debian.org/l10n-pkg-status/b/boinc.html > indicates a few issues. I then ran > msgfmt -c -o /dev/null <po file> > as indicated and for de.po prepared the attached patch. > > Cheers, > > Steffen > > > ------------------------------ > > Message: 3 > Date: Tue, 28 May 2013 18:14:03 +0200 > From: Christian Beer <[email protected]> > To: Rom Walton <[email protected]> > Cc: [email protected] > Subject: Re: [boinc_dev] [patch] .po files with issues > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Yes, but I will test them first on a local server as I'm not sure that > this will work with our i18n implementation. > > Regards > Christian > > Am 28.05.2013 17:46, schrieb Rom Walton: >> Christian, >> >> Could you apply these changes to http://boinc.berkeley.edu/translate? >> >> If we just commit them to the source tree, they will be overwritten the > next time we pull from the translation system. >> >> ----- Rom >> >> -----Original Message----- >> From: boinc_dev [mailto:[email protected]] On Behalf Of > "Steffen M?ller" >> Sent: Friday, May 24, 2013 5:11 PM >> To: [email protected] >> Subject: [boinc_dev] [patch] .po files with issues >> >> Hello, >> >> Debian performs a routine check on the .po files in all its packages. The > one of BOINC http://i18n.debian.org/l10n-pkg-status/b/boinc.html >> indicates a few issues. I then ran >> msgfmt -c -o /dev/null <po file> >> as indicated and for de.po prepared the attached patch. >> >> Cheers, >> >> Steffen >> > > > > ------------------------------ > > Message: 4 > Date: Tue, 28 May 2013 13:33:20 -0700 > From: David Anderson <[email protected]> > To: Toralf F?rster <[email protected]>, BOINC Developers Mailing > List <[email protected]> > Subject: Re: [boinc_dev] 7.1.2 compile failed at a stable Gentoo Linux > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > We added a Makefile.am to html/ so that "make install" would copy PHP > files. > -- David > > On 28-May-2013 1:04 PM, Toralf F?rster wrote: >> On 05/28/2013 08:34 PM, David Anderson wrote: >>> Did you do >>> >>> ./_autosetup >>> ./configure >>> make >> 7.1.2 build s and runs fine here now. >> >> The issue qas related to the Gentoo ebuild which removed the html >> sources from the tarball in the past b/c they weren't used. >> >> I adapted the ebuild -but - will be the html sources are now mandatory ? >> > > > ------------------------------ > > Message: 5 > Date: Tue, 28 May 2013 22:56:59 +0200 > From: Toralf F?rster <[email protected]> > To: "[email protected]" <[email protected]> > Subject: [boinc_dev] could the git comment be more descriptive or > better empty ? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > It would be sometimes helpful for 3rd party > testers/reviewers/people_which_are_just_interested if the git comments > would be more descriptive or completely empty to not waste space, > especially comments shouldn't tell what was changed but why a change was > made, or ? > > > -- > MfG/Sincerely > Toralf F?rster > pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 > > > ------------------------------ > > Message: 6 > Date: Tue, 28 May 2013 13:59:43 -0700 > From: David Anderson <[email protected]> > To: [email protected] > Subject: Re: [boinc_dev] could the git comment be more descriptive or > better empty ? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Please give examples of non-descriptive comments. > -- David > > On 28-May-2013 1:56 PM, Toralf F?rster wrote: >> It would be sometimes helpful for 3rd party >> testers/reviewers/people_which_are_just_interested if the git comments >> would be more descriptive or completely empty to not waste space, >> especially comments shouldn't tell what was changed but why a change > was >> made, or ? >> >> > > > ------------------------------ > > Message: 7 > Date: Wed, 29 May 2013 00:38:40 +0200 > From: Jorden van der Elst <[email protected]> > To: David Anderson <[email protected]> > Cc: BOINC Dev Mailing List <[email protected]> > Subject: Re: [boinc_dev] could the git comment be more descriptive or > better empty ? > Message-ID: > <caexjb0c_qfp7ukvd4pg+sxjwbgccdfw0rmicrxftvhoshk8...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I'd rather that there'd be a more uniform use the prefixes. That > everyone use the same prefix, so that those of us keeping change logs > can see a bit easier what goes where. > Now there's a couple of entries that say client, but are android. Or > some entries that have no prefix whatsoever, and only by opening the > whole commit and checking what files were they changed in, can we > determine if it was a change for the change log or not. > > Like these: > android > API > client > condor > db-purge > MGR > scheduler > server > web > > Now one person does Client, the other client, the third nothing. > Or one person uses mgr, the other MGR, then a third says Manager, etc. > It would also be nice if all sentences ended with a full stop, but > perhaps that's just wishful thinking. :-) > > As for 'non-descriptive comments', we all hate the 'quick > updates', or > 'quick fixes'. I just take it that sometimes those cannot be helped. > > On Tue, May 28, 2013 at 10:59 PM, David Anderson <[email protected]> > wrote: >> Please give examples of non-descriptive comments. >> -- David >> >> >> On 28-May-2013 1:56 PM, Toralf F?rster wrote: >>> >>> It would be sometimes helpful for 3rd party >>> testers/reviewers/people_which_are_just_interested if the git comments >>> would be more descriptive or completely empty to not waste space, >>> especially comments shouldn't tell what was changed but why a > change was >>> made, or ? >>> >>> >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. > > > > -- > -- Jord van der Elst. > > > ------------------------------ > > Message: 8 > Date: Tue, 28 May 2013 16:08:43 -0700 > From: Charlie Fenton <[email protected]> > To: Toralf F?rster <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [boinc_dev] could the git comment be more descriptive or > better empty ? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=iso-8859-1 > > Hi Toralf, > > By "what has changed" do you mean the list of modified files or a > brief description / explanation of what has changed? > > For those of us who use a GUI interface to GIT like SourceTree, it is _very_ > helpful for the GIT commit message to start with a brief description of > _what_ > has changed. SourceTree (which I highly recommend) presents a list of > commits > as one line each, with the first part of the commit message shown for each. > This allows us very quickly to see what has changed with each commit without > needing to examine each one individually. > > I agree with Jord that 'quick updates', or 'quick fixes' is not > helpful, but I also don't want to see empty commit messages. I feel that > _every_ commit should have a commit message briefly describing what was > changed > and why. > > Cheers, > --Charlie > > On May 28, 2013, at 1:56 PM, Toralf F?rster wrote: > >> It would be sometimes helpful for 3rd party >> testers/reviewers/people_which_are_just_interested if the git comments >> would be more descriptive or completely empty to not waste space, >> especially comments shouldn't tell what was changed but why a change > was >> made, or ? >> >> >> -- >> MfG/Sincerely >> Toralf F?rster >> pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > > > ------------------------------ > > End of boinc_dev Digest, Vol 108, Issue 20 > ****************************************** > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
