Activity for snownews
-
Strahinya Radich posted a comment on merge request #3
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...
-
Mike Sharov posted a comment on merge request #3
Your changes do not convert escaped newlines to multiline strings, but convert single line strings to multiline strings by wrapping them at some arbitrary limit. For example, the first change in your diff breaks "Unsafe browser string. See snownews.kcore.de", splitting it just after "See ". If I understand the new gettext recommendation correctly, that would create a line break there, preventing gettext from matching the original single line string. You can't see it, of course, just by running msgfmt,...
-
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....
-
Running configure errors out
-
Closing "wontfix". Will later consider revising supported OS list.
-
It appears that your shell is being overly aggressive in unescaping the slashes in the string that builds config.sed. I am /extremely/ wary of messing with string escaping, since this has previously been a recurring problem on various platforms. The current code has been tested and worked on BSD previously (FreeBSD), and it does work when using dash, which is the only ksh equivalent I have access to. Since I am not able to repeat the extensive testing required to verify that any proposed fixes would...
-
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...
-
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....
-
po/sr.po: Update translator's email address
-
I've done the email change manually. Commit 351dd7ebbb81109a090c5d90c3817c4f44278c08.
-
Update Serbian translator's email
-
Please attach the failing config.sed. I am not able to reproduce the error when running the specified command. Calling escpath the way you do is not appropriate; it is supposed to take the unescaped path as the argument.
-
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, which will prevent gettext from finding your translations. If you want this committed, you need to do just the email address change and remove all the others. You can submit them in another MR.
-
Running configure errors out
-
po/sr.po: Update translator's email address
-
Replace deprecated htmlEntityLookup with xmlGetPredefinedEntity
-
Use libunistring for unicode processing
-
Convert to C++
-
Error creating cache directory during setup
-
Fixed by commit 5d4ec642056ee5c7348c00a5b18e9ddf3b81c785
-
Error creating cache directory during setup
-
Create parent dirs during snownews dirs setup
-
slacker created ticket #79
Internal error running after build from source
-
Replace deprecated xmlRecoverMemory call
-
snownews updated /README.md
-
-
Bump version number for release
-
Fix smartfeed prev for first item + fix smartfeed item read status saving
-
Merged with 7c1f248f34029bb2252b048a185c49ffc15ef443 and b71ca89dac1c476e20ccaf68dbaef211963a4c92.
-
Fix saving newsitem read status from smartfeeds
-
Fix missing prev link on first add smartfeed item
-
Mr. P created merge request #2 on Code
Fix smartfeed prev for first item + fix smartfeed item read status saving
-
Fix for smartfeed "previous" button
-
Yes, the prev link should have been updated. I've merged as 3fbe4d52a0507a6841d28954febe7e32e5ed44fc. (Due to the extra braces on the if in your code, which I don't do)
-
Fix missing prev link on add smartfeed item
-
Fix for smartfeed "previous" button
-
Move project to Sourceforge
-
-
-
-
-
-
-
-
-
1
