# 2024-12-26 13:37:00.133769 UTC (+0000)

sfeed 2.1 was released.

sfeed is a tool to convert RSS or Atom feeds from XML to a TAB-separated file.

It can be found at:
 * git://git.codemadness.org/sfeed
 * gopher://codemadness.org/1/git/sfeed
 * https://codemadness.org/releases/sfeed/
 * gopher://codemadness.org/1/releases/sfeed/

sfeed has the following changes compared to 2.0:


Fixes:

* xml.c parsing fix: improve parsing whitespace after end tag names.
* sfeed_update: fix: leave IFS unchanged for sfeedrc code.

Other improvements:

* sfeed.c, small pedantic time parsing improvements:
 * support , for decimal fractions (and timezone suffix).
 * support / as a year/month/day separator.
   Using this separator is not in the standard and actually incorrect, but can be
   supported without breaking anything.
 * support lowercase T separator in RFC3339 timestamps.

* sfeed_update: separate the logic of running feeds in a function.
 It can be used to more easily replace the logic of running feeds with xargs
 with something else like GNU/parallel or the previous behaviour which didn't
 require xargs.

* util.h: add a comment/note about __dead and noreturn hints.
 All the current clang analyzer warnings are false-positives.

* Documentation improvements
 * Add ETag and bandwidth saving example to sfeedrc.5 man page.
 * Add example to replace xargs with the previous behaviour in sfeed_update,
   which used a pure POSIX shell way to process feeds.
 * Some rewording and consistency improvements.
 * Typo and spelling fixes.

* Makefile: make install: on install do not follow symlinks and just copy them.
 Not neccesary but it is used for my local script to bundle the sfeed tools
 and compile/link and symlink them in a compact way (similar to busybox).

* Small code-style improvements.


Have a good holiday,

Thanks for all feedback and patches,
Hiltjo

You are viewing proxied material from bitreich.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.