From: Dan Callaghan <djc@djc.id.au>
To: supmua <supmua@googlegroups.com>
Subject: release 1.1
Date: Mon, 23 May 2022 21:06:21 +1000 [thread overview]
Message-ID: <1653303605-sup-4606@sage.djc.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
I've just released Sup 1.1. It includes various bug fixes around
character encodings, plus Ruby 3.0 and 3.1 support.
The new release is available from Rubygems and Github.
== 1.1 / 2022-05-23
* #588, #577: Sup is now compatible with and tested on Ruby 3.0 and Ruby 3.1.
(Dan Callaghan)
* When the Sup gem installs xapian-ruby, it will install to the user gem
directory if the system gem directory is not writable. (Iain Parris)
* #571: To and From addresses of enclosed messages are now displayed normally,
instead of as Redwood::Person objects. (Iain Parris)
* #570: Fixed wording when displaying enclosed messages without Date header.
(Iain Parris)
* #205, #602: UTF-8 header values are now accepted and handled correctly, as
per RFC6532. (Dan Callaghan)
* #585: Text/plain attachments with invalid charset are now displayed as
US-ASCII (with high bytes replaced) instead of crashing. (Dan Callaghan)
* #424: Spaces are now accepted in RFC2047-encoded header words, even though
the RFC forbids them. (Dan Callaghan)
* Invalid RFC2047-encoded header words are now displayed in their raw form,
rather than trying to forcibly transcode them to UTF-8, as per the RFC's
recommendation. (Dan Callaghan)
* Sup now decodes UTF-7 correctly instead of crashing. (Dan Callaghan)
--
Dan Callaghan <djc@djc.id.au>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-05-23 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1653303605-sup-4606@sage.djc.id.au \
--to=djc@djc.id.au \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox