Bug#1032812: marked as done (Allow user to influence Content-Transfer-Encoding)
Your message dated Sun, 12 Mar 2023 09:51:15 +0100
with message-id <ce451a7b-0766-b110-70ad-98e8ec78be09@mailbox.org>
and subject line Re: Bug#1032812: Allow user to influence Content-Transfer-Encoding
has caused the Debian Bug report #1032812,
regarding Allow user to influence Content-Transfer-Encoding
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1032812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032812
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 11.6.0
Severity: minor
Allow user to influence Content-Transfer-Encoding.
Don't just leave it up to the whims of the program.
$ < /dev/null HOME=/dev/null reportbug ca-certificates --template|grep Encoding
Content-Transfer-Encoding: base64
$ < /dev/null HOME=/dev/null reportbug reportbug --template|grep Encoding
Content-Transfer-Encoding: 7bit
For instance, the user might want a template readable by another
program, without needing to add a decoding checking step.
--- End Message ---
--- Begin Message ---
On 12.03.2023 00.23, Dan Jacobson wrote:
> Allow user to influence Content-Transfer-Encoding.
Reportbug does not even "influence the Content-Transfer-Encoding"
itself. Python's email library takes care of setting this to a suitable
value for us.
> For instance, the user might want a template readable by another
> program, without needing to add a decoding checking step.
There are no plans to support such a use case. Anyone who wants to write
a proper email parser will need to be able to deal with different
encodings anyway. And there are already capable email parsers around in
many languages, so most people don't have to write their own.
No bug here, closing.
--- End Message ---
Reply to: