Since Rafal's original inquiry, I have modified the email notification
logic to use quoted-printable instead of base64.  Quoted-printable is
not as clean as plain-old 8bit, but it is much more readable than
base64.  Acceptable compromise?

On 6/26/18, Rafal Bisingier <ra...@itec.com.pl> wrote:
> Hi
>
> Richard asked me to post it on the list for discussion, so here it is:
> The new email notification functionality in fossil use base64 as
> Content-Transfer-Encoding. I personally prefer use of 8bit encoding,
> which have a side-effect of human-readable source of message. I admit
> that it does not matter much in a normal situation (reading the message
> in an email client), but on a few occasions I had to grep/cat through
> mailbox files, and having a readable message body was of great help
> then. That's why I want to submit for consideration using a 8bit
> content transfer encoding for email notifications. Nowadays there are
> practically no problems in transport of such messages. The only down
> side I could think of is that theoretically there is a limit of 1000
> chars in a line in an email message (and base64 encoding bypasses it).
> But would it really be a bigger problem?
> On the pros there is simplified debugging (no need to decode message,
> which fossil store in his database file in "transport-ready" form -
> so currently with base64 encoded body). Of course DRH already wrote a
> tool to help in this ;-) so it is already doable without much trouble
> https://www.fossil-scm.org/fossil/file/tools/decode-email.c
> Nevertheless I'd like to have a readable source of messages. ;-)
>
> --
> Greetings
> Rafal Bisingier
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>


-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to