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 <[email protected]>

-- 
You received this message because you are subscribed to the Google Groups "The 
Sup email client" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/supmua/1653303605-sup-4606%40sage.djc.id.au.

Attachment: signature.asc
Description: PGP signature

Reply via email to