2020-01-11 11:50:54 UTC
* Display article from "news" type URI in separate window
(if it's not found in current group)
* Clickable References added to article window
* Search for Message-ID added ("Tools->Search Message-ID" or Ctrl-s)
* Command line option "-4" added (force usage of IPv4 network protocol)
* Decoder for RFC 3676 "flowed" format modified: The 'flowed_insert_crlf'
entry in configfile can add an empty line separator after every
paragraph that ends with an empty line.
* The behaviour of 'flowed_insert_crlf' can be requested by the sender
of an article with the experimental parameter "InsLine=yes" in the
Content-Type headerfield (see background section below)
* TLS modules compile time option 'CFG_USE_TLS_OWNCERTS' replaced by
new 'tls_owncerts' entry in configfile
* TLS module now supports new 'crl_check' entry in configfile (ignored
if compile time option CFG_TLS_CRLS_DISABLE is nonzero)
* OpenSSL 3 is now supported (required for negotiation of RFC 7919 FFDHE
groups with TLSv1.2 and TLSv1.3 protocols)
* LibreSSL 3 is now supported
* Normalization based on Unicode 12.1.0
Full changelog, Sourcecode, Documentation, etc.:
Background for experimental "InsLine" parameter
RFC 3676  specify that a paragraph must contain at least 2 lines:
| paragraph = 1*flowed-line fixed-line
| ; all lines in paragraph MUST be unquoted or
| ; have same quote depth
For narrow displays, e.g. on Smartphones, it may be intended that all
text can be rewrapped for presentation. If the text for a paragraph
is e.g. 65 characters, it will fit on a single line with the 78-
character wrapping recommended for article generation. But to make it
a paragraph in the syntax of RFC 3676, it must be wrapped too early
(wrapped trailing part as fixed-line) or an empty fixed-line must be
appended (in addition to a paragraph separation line, if present).
Both variants look ugly if the article is interpreted as fixed format.
Some people therefore generate flowed articles in a way that all its
paragraphs end with an empty line (by using/abusing separation lines
intended for fixed format to terminate the paragraphs).
This looks ugly if viewed as flowed format, if no additional indentation
is created by the flowed decoder at the beginning of paragraphs (because
there is no vertical space between paragraphs anymore).
The "InsLine=yes" parameter is intended to declare that the sender has
used empty separation lines as paragraph termination and that the flowed
decoder should recreate them for presentation.
[Xpost and Fup2 news.software.readers]