Is there some sort of automated tool we could run to catch this \n mismatch error? It seems to come up quite frequently; and since we are taking translations automatically, it can happen on any checkin. Most often it happens on the "Translator Credit" strings. It would be nice if git builds all the time, not just when we do a release.
Let me reemphasize that released tarballs must build. The way I do it is to make dist, and then build and install the tarball in my build area as if I were an ordinary user downloading and installing the new release. Only then do I check in the release bump and upload the tarball to SF. In the last day or so we had a case where a package failed to build because the dependency checking was missing/incorrect in configure. This is another thing that developers must be sensitive to. If you are writing GTK/Glib code, you need to check the "Since" notation in the documentation, satisfy yourself it makes sense from a product perspective to depend on the newer version, and update your version check. We want people to have configure failures rather than build failures. If you add a displayable string, make sure it is marked for translation and before you release anything in tarball form, there needs to be notice to the translation team and a delay to get the translations finished. We have far too many users now to be sloppy about this, and an approval rating anyone would be proud of to defend. I see that Christoph has made further comments while I was writing, which I totally support. On 04/06/2010 10:04 AM, Martin Bagge / brother wrote: > On Tue, 6 Apr 2010, Angel Velásquez wrote: > >> I was trying to build lxtask 0.1.2 to make the package for Arch Linux, >> then I found a message on fa.po (and other files, I corrected by hand >> fa.po and tried to build again), the message is like this: >> >> fa.po:39: `msgid' and `msgstr' entries do not both end with '\n' >> >> Any hints? am I doing something wrong (I don't wanna believe is an >> error of most of .po files) > > For fa.po there is a pretty major error where the translator left parts of > the string out. I am not sure why and if it could be an accident. > In the repo I just added the "missing" parts and that might break things > so I have noted the string as fuzzy too - demanding a review. > > This is how it looks before > #: ../src/xfce-taskmanager-linux.c:385 > #, c-format > msgid "" > "Couldn't send signal %d to the task with ID %d\n" > "\n" > "%s" > msgstr "ناتوانی در ارسال علامت %d برای وظیفه با مشخصه %d\n" > > The missing part is the new line and %s and I just added those. > > There are no other errors reported so you have to be more specific about > fi, fr and frp for me thos see those. > > See commit 8e63ead504bc21437110e94f0a169c1f937ee82d > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
