Strahinya Radich

If I understand the new gettext recommendation correctly, that would create a line break there, preventing gettext from matching the original single line string. What "new gettext recommentation"? String literals in C can be split like this: #include <stdio.h> int main() { const char *s = "Hello" "world"; printf("%s\n", s); } which prints Helloworld Gettext "strings" follow the same logic, as described in the GNU Gettext manual. This was the case at least since I first learned about Gettext around...

At some point I may just list OpenBSD as explicitly unsupported. Well, snownews is already present as a port www/snownews, which is built by applying the above linked patch, so I think there is no need.

This commit does way more than just update your email address. You appear to have rewritten the entire file, in many cases rewrapping the english match strings, Yes, since I am using my own .po file editor, poe. Generally, invoking the update-pot target in Makefiles generated by autotools would be enough to minimize the differences in wrapping in the saved file. Unfortunately, I see no such target in snownews. which will prevent gettext from finding your translations. I'm sorry, but this is false....

Please attach the failing config.sed. Sure, it is attached with this reply. By the way, the output above (with line number 33) was made after several runs of ./configure, so the file config.sed has accumulated a lot of lines. With config.sed not existing prior to running ./configure, the error message is: $ ./configure --builddir=build --mandir=/usr/local/man sed: 4: config.sed: bad flag in substitute command: 'u' sed: 4: config.sed: bad flag in substitute command: 'u' for the attached config.sed...

Please attach the failing config.sed. Sure, it is attached with this reply. By the way, the output above (with line number 33) was made after several runs of ./configure, so the file config.sed has accumulated a lot of lines. With config.sed not existing prior to running ./configure, the error message is: $ ./configure --builddir=build --mandir=/usr/local/man sed: 4: config.sed: bad flag in substitute command: 'u' sed: 4: config.sed: bad flag in substitute command: 'u' for the attached config.sed...

Please attach the failing config.sed. Sure, it is attached with this reply. By the way, the output above (with line number 33) was made after several runs of ./configure, so the file config.sed has accumulated a lot of lines. With config.sed not existing prior to running ./configure, the error message is: $ ./configure --builddir=build --mandir=/usr/local/man sed: 4: config.sed: bad flag in substitute command: 'u' sed: 4: config.sed: bad flag in substitute command: 'u' for the attached config.sed...

Please attach the failing config.sed. Sure, it is attached with this reply. By the way, the output above (with line number 33) was made after several runs of ./configure, so the file config.sed has accumulated a lot of lines. With config.sed not existing prior to running ./configure, the error message is: $ ./configure --builddir=build --mandir=/usr/local/man sed: 4: config.sed: bad flag in substitute command: 'u' sed: 4: config.sed: bad flag in substitute command: 'u' for the attached config.sed...

Please attach the failing config.sed. Sure, it is attached with this reply. By the way, the output above (with line number 33) was made after several runs of ./configure, so the file config.sed has accumulated a lot of lines. With config.sed not existing prior to running ./configure, the error message is: $ ./configure --builddir=build --mandir=/usr/local/man sed: 4: config.sed: bad flag in substitute command: 'u' sed: 4: config.sed: bad flag in substitute command: 'u' for the attached config.sed...